Develop Bugs

application file cannot be opened .either it is notsigned with trusted certificate

I am having problems with applications under Windows Mobile 5.0. When i try to run them i get the following error.
The file 'foo' cannot be opened. Either it is not signed with a trusted certificate, or one of its components cannot be found. You might need to reinstall or restore this file.
1)Is there anyway of disabling the checks for trusted applications in Windows Mobile 5.0 on the Wizard?

I think this error becuz u r trying to run wm6 applications under wm5

vodovodo said:
I think this error becuz u r trying to run wm6 applications under wm5
Click to expand...
Click to collapse
I have same problem for BA wm 6.1 5.2.19199.1.0.0 PV DVH. Some people offered solution of HR. I don't agree with this. because we have to lose what we've been installing and spend more time re-installing them. so much time-wasting?
Any other solutions, please?!
Thanks in advance.

Problem may be cause of your SD card if u r using WM6. SD card PowerManagment value is set("DisablePowerManagment") to 0 in your registry. This means after a while your device will set your SD card power off for savg batttery. This cause to unread your program files etc while u start any program on your form your SD card device.
I fixed this problem like that;
By any registry editor:
Find the Path:
"Hkey_local_machine>drivers>sdcard>clientdrivers> class >SDMemory_Class"
after that find;
""DisablePowerManagement"" key and set its value to "1" than save and exit. Than soft reset your device. Problem will be fixed.
Sorry for my bad english.

Windows Mobile powered devices are shipped with default security settings.
The security model enables Mobile Operators to make post-production changes to security settings.
This can place significant restrictions on software which has not been signed and approved.
However you can change the default settings.
Take control of applications on your phone.
"All listed settings are decimal"
1. Connect the phone through ActiveSync.
2. Run your favorite remote registry editor "CeRegEditor (Download)" "Mobile Registry Editor (Download)" on your PC. http://ceregeditor.mdsoft.pl/
3. Navigate to HKEY_LOCAL_MACHINE\Security\Policies\Policies
Unsigned Prompt Policy:
This policy indicates whether the user is prompted to accept or reject unsigned .cab, theme, .dll and .exe files.
HKEY_LOCAL_MACHINE\Security\Policies\Policies
DWord = 0000101a Data = Use the following-->
0 = Indicates user will be prompted.
1 = Indicates user will not be prompted.
you will set that register decimal 1. that is solved problem

I have a HTC Tytn II and i get the same error. However, When trying to alter data using the reg editor you recommended, i found the 0000101a was already set to 1. Any other ideas?

Hi All,
Would someone be so kind to me a explain how I can move a package from the EXT directory or one Kitchen to the EXT directory on this version of kitchen.
I thought I could just simply copy the directory? So I had a go compiling a version of youtube from a different kitchen It would seem mot to work thou as I get the dreaded The file 'xx' cannot be opened. Ether it is not signed with a trusted certificate, or one of its components cannot be found. If the problem persists, try reinstalling or restoring the file.
Any ideas how to get this to work?

Or look for the tool MsSigner, it can be found in most kitchens.
You'll be able to sign it with a signature that is accepted after you aply the enablyRapi and SPCCerts policies.

You're probably missing a key dependency package like dshow (mshow?) or concurrence manager. Also, make sure the shortcut path is valid. Lord knows why, but that's the message you get for bad shortcuts.

josephwsl said:
I am having problems with applications under Windows Mobile 5.0. When i try to run them i get the following error.
The file 'foo' cannot be opened. Either it is not signed with a trusted certificate, or one of its components cannot be found. You might need to reinstall or restore this file.
1)Is there anyway of disabling the checks for trusted applications in Windows Mobile 5.0 on the Wizard?
Click to expand...
Click to collapse
maybe .NET CF is missing or not up-to-date?

RAMMANN said:
maybe .NET CF is missing or not up-to-date?
Click to expand...
Click to collapse
ahh i love you bro, u saved me an hassle i tried everything and it was the net.cf

damii said:
you will set that register decimal 1. that is solved problem
Click to expand...
Click to collapse
When I try that, I'm told I don't have the authority to access that. :-(
now what?

Yeah, me too!!!
All of a sudden too. Everything was fine then I got these certificate errors every time I try to run Haret.exe to run android. This happened last night. Did my provider change something on me?
I try to change that registry key and it won't let me.

Re:this post
I have same problem for BA wm 6.1 5.2.19199.1.0.0 PV DVH. Some people offered solution of HR. I don't agree with this. because we have to lose what we've been installing and spend more time re-installing them. so much time-wasting?

You need hard reset!

Same problem "certificate errors" and a hard reset wont work
Plz help

damii said:
Windows Mobile powered devices are shipped with default security settings.
The security model enables Mobile Operators to make post-production changes to security settings.
This can place significant restrictions on software which has not been signed and approved.
However you can change the default settings.
Take control of applications on your phone.
"All listed settings are decimal"
1. Connect the phone through ActiveSync.
2. Run your favorite remote registry editor "CeRegEditor (Download)" "Mobile Registry Editor (Download)" on your PC.
3. Navigate to HKEY_LOCAL_MACHINE\Security\Policies\Policies
Unsigned Prompt Policy:
This policy indicates whether the user is prompted to accept or reject unsigned .cab, theme, .dll and .exe files.
HKEY_LOCAL_MACHINE\Security\Policies\Policies
DWord = 0000101a Data = Use the following-->
0 = Indicates user will be prompted.
1 = Indicates user will not be prompted.
you will set that register decimal 1. that is solved problem
Click to expand...
Click to collapse
Thanks! That really helped me. You literally saved me a good night sleep. I was already desperate.

Wow, it works Thank you!!!

Awesome!!!
This worked perfectly. Thanks so much for the help. I've been racking my brain about this for over an hour now, then found this through a search.
Thanks!

OMG
I have the same problem and I tried :
1/ Hard Reset
2/ Rom Update
3/ installed NetCFv3.5
4/ editing values in the registry
what els ????!
plzz i need your help

Starting custom executables in phone

One way to start custom executabled in windows phone 7 is following method:
1) create a exe file that runs in phone
2) create a zip file and put exe inside
3) upload zip file to some internetpage and create .html page for it with <a href.. link for it.
4) navigate to the page with phone IE.
5) when clicking the link the phone can open the zip file and display its contents (tap to open the file ...zip)
6) when clicking the .exe file the phone asks are you sure you want to run
(The program ...exe is from an unknown publisher. Running it could harm your phone. Do you want to continue?)
7)enjoy your homebrews

will this also work on a phone that isn't developer unlocked ?
if that is right than this is the ultimate way to jailbreak a wp7 phone

Never-mind

Nope, he isn't, and described above method works (I guess because of MS ZipView executable bug). But I can't get my apps running, probably because they are not compatible with CE 7.0 and WP7 .Net (I've tried CE 6.0 native code and .NET code).

sensboston said:
Nope, he isn't, and described above method works (I guess because of MS ZipView executable bug). But I can't get my apps running, probably because they are not compatible with CE 7.0 and WP7 .Net (I've tried CE 6.0 native code and .NET code).
Click to expand...
Click to collapse
is your phone developer unlocked ?

Yes, unlocked.

sensboston said:
Yes, unlocked.
Click to expand...
Click to collapse
**** bummer , do you have a web link to that test file of yours then I can try it my phone is locked

xttp://home.comcast.net/~sergsv/
There are two links to zip archives at the left top corner of the page. I can't run these files but MS zip archiver open these zips and asked to run

yes man this is working on a locked phone

now we need some code that works to test this
lets say an .exe that run the file explorer

yes. right now we don't know whether the apps are opened at all. Are the managed Apps in VS compiled into an exe? Maybe we could extract one from an xap for testing purposes...

Silverlight XAPs use XAMLs and DLLs, no EXEs involved I'm afraid.

Hmm yes you're right. Are there extracted executables from the leaked Mondrian ROM?

There are, but they are not GUI apps, they look mainly like command line executables provided by Qualcomm, and some of them look like they could mess up your phone if you don't know what you're doing.
There are some GUI apps, but they come disassembled. I've been trying to assemble them but haven't had much luck yet.

Neat. I shall put together a sample application to test this. (I have Visual Studio 2010 configured to pump out CE7 native executables.)

I think the executable run is blocked. They left typical MS (say - stupid) dialog box but, I believe, ignore the user input...
However the Word and Excel documents can be opened this way.

I tried a few things -- rebooting the phone, crashing the program with invalid pointers, and launching some known executables. Nothing. I even signed my executable with a valid certificate; It still claims unknown publisher.
Wonder if this is some left over dialog as mentioned by sensboston

WithinRafael said:
I tried a few things -- rebooting the phone, crashing the program with invalid pointers, and launching some known executables. Nothing. I even signed my executable with a valid certificate; It still claims unknown publisher.
Wonder if this is some left over dialog as mentioned by sensboston
Click to expand...
Click to collapse
The dialog will be hidden by the shell. You need to add your cert into the phone, email it, resign your app and try it again.
It's possible it'll work.

this will only work with MSFT signed exe's.

walshieau said:
this will only work with MSFT signed exe's.
Click to expand...
Click to collapse
I tried with both my signed executable (with Root CA cert installed) and a Microsoft executable. Neither show signs of execution.

[REF] How to quickly load your Live Activation Code to device by installing an .xap

[FONT=&quot]If I mention anything about how to quickly side load your Live Activation Code using an .xap in the forums I am often asked to explain it. So this is clarifying how to quickly load your Activation code using an .xap created using xboxmod’s WP7 Registry tweak and the AdvancedConfig_1.1.0.1_beta (included in the [/FONT][FONT=&quot]attached [/FONT][FONT=&quot]Rgu-2-xml.rar) (ALL acknowledgment and thanks to xboxmod and the contributors to that forum).[/FONT]
Although there a number of steps shown, it is actually a quick and easy process.
[FONT=&quot]Note, this is not about getting your Activation code - you must already have your Activation code!!! There is considerable discussion in the forums about obtaining an activation code if you do not already have one. It is about applying it easily after each Hard Reset or Rom install. (see footnote)[/FONT]
[FONT=&quot]So here's how to set the Activation code by installing an XAP rather than entering all those characters manually. It is much easier and worth the few minutes to setup. Simply make this the first App you install before you log into Windows Live using your email address etc. or the Marketplace - it does not ask you for you Activation code after this is run as it is already in the registry.[/FONT]
Ensure that you have Connection Setup installed
[FONT=&quot]1. Create a txt document (e.g. WP_Activation_Code.txt) exactly (ensure you have REGEDIT4 as the first line)[/FONT] as follows
Code:
REGEDIT4
[HKEY_LOCAL_MACHINE\Software\Microsoft\GwpCPC]
"ActivationCode"="*****-*****-*****-*****-*****"
[FONT=&quot]WHERE: *****-*****-*****-*****-*****" is your Activation Code[/FONT]
[FONT=&quot]Take care with the code ActivationCode"="*****-*****-*****-*****-*****" The "-" are not underscore "_", though they look like it, but dashes "-" (hyphens). I got caught with this at my first attempt.[/FONT]
[FONT=&quot]2. Rename this text file from .txt to .reg (e.g. WP_Activation_Code.reg)[/FONT]
[FONT=&quot](suggestion: make a copy of the file and rename the copy)[/FONT]
[FONT=&quot]3. Run xboxmod's Rgu-2-xml.exe (from attached .rar) to translate this text file to a provxml[/FONT]
[FONT=&quot]4. Rename this file (e.g. mxipupdate_WP_Activation_Code.provxml) to simply CustClear.provxml[/FONT]
[FONT=&quot]5. Extract AdvancedConfig 1.1.0.1 beta.xap (from attached .rar - I added this and the org. instructions to this .rar).[/FONT]
[FONT=&quot]6. Rename it to HTC-ProvXml-WP_Activation_Code.xap[/FONT]
[FONT=&quot]7. Open it with 7-Zip or WinRAR (right click on HTC-ProvXml-WP_Activation_Code.xap and select open).[/FONT]
[FONT=&quot]8. Copy custclear.provxml into HTC-ProvXml-WP_Activation_Code.xap and replace the existing custclear.provxml with custclear.provxml file you just created.[/FONT]
[FONT=&quot]9. Install (sideload) the HTC-ProvXml-WP_Activation_Code.xap to your device - it will load as HTC-ProvXml-Deploy. [/FONT][FONT=&quot]Install it [/FONT] like any other app - use an xap deployer.
[FONT=&quot]
(you can use this file each time you hard reset or load a new rom. Suggestion make it the first xap you install after initial Zune connection before you register for Marketplace or Live).[/FONT]
[FONT=&quot]10. Launch HTC-ProvXml-Deploy on your device.[/FONT]
[FONT=&quot]11. Press the green button to apply your settings.[/FONT]
[FONT=&quot]12. Uninstall HTC-ProvXml-Deploy then reboot to be sure. [/FONT]
[FONT=&quot]13. Now login to Marketplace or Live without entering the code manually :good:[/FONT]
[FONT=&quot]Works a treat and skips the Live Code step. You can then use it more than once - each time you load a rom or hard reset for example.[/FONT]
[FONT=&quot]For further instructions and the many applications for xboxmod’s WP7 Registry tweak application HTC-ProvXml-Deploy see:[/FONT]
[FONT=&quot]http://forum.xda-developers.com/showthread.php?t=907971 [/FONT]
[FONT=&quot]Note:[/FONT]
[FONT=&quot]The Activation code is required when signing in with a Windows Live ID on your Windows Phone 7[/FONT]
[FONT=&quot]The first time that you sign in with your Windows Live ID on Windows Phone 7 you may see the following message prompting you to enter an activation code: [/FONT]
Code:
[FONT=&quot]ACTIVATION REQUIRED[/FONT]
[FONT=&quot]An activation code is required before we can finish setting up your [/FONT]
[FONT=&quot]Phone. Please contact customer service. You can skip this step and do it [/FONT]
[FONT=&quot]later.[/FONT]

This s a nice idea - saves time when installing Roms.
An additional note: Need to have Connection Setup installed and phone network connected

oucha said:
This s a nice idea - saves time when installing Roms.
An additional note: Need to have Connection Setup installed and phone network connected
Click to expand...
Click to collapse
Yes, true - you need to have Connection Setup installed as it relies on this to change the settings in registry - this enters the Live Activation Code in device registry
Although there a number of steps shown, it is actually a quick and easy process.
The xap can then be reused many times

oucha said:
This s a nice idea - saves time when installing Roms.
An additional note: Need to have Connection Setup installed and phone network connected
Click to expand...
Click to collapse
I've added this to the above instructions
Thanks

Nice tutorial,
But I think you could save time with using my reg backup app and apply the .reg file with that

EaterOfCorpses said:
Nice tutorial,
But I think you could save time with using my reg backup app and apply the .reg file with that
Click to expand...
Click to collapse
I have check your idea, but one would need to load your code in the first place, so this still has a place. Once you set it app you just run it as the first app.
So I'm waiting at this stage

Hi
I did all of this and everything that was in the description but it did NOT work.
The problem was that when I deployed the XAP file the Advanced Config Tool was updated and it never started.
I didn't get a new app installed on my phone since the XAP that I had to modify was the Advanced Config Tool.
So, what did I miss?
Thanks in advance.

Skateout said:
Hi
I did all of this and everything that was in the description but it did NOT work.
The problem was that when I deployed the XAP file the Advanced Config Tool was updated and it never started.
I didn't get a new app installed on my phone since the XAP that I had to modify was the Advanced Config Tool.
So, what did I miss?
Thanks in advance.
Click to expand...
Click to collapse
Sorry, I missed this one
Not sure why it did not work.
What is the connection with Advanced Config Tool?
Is Connection Setup installed? What Rom are you using?

windows rt rtm

MICROSOFT.WINDOWS.RT.8.1.WITH.OFFICE.2013.RT.RTM.WOA.ENGLISH.DVD-WZT
MICROSOFT.WINDOWS.RT.8.1.ADK.KIT.WOA.RTM-WZT
Thats all I want to say

windowsrtc said:
MICROSOFT.WINDOWS.RT.8.1.WITH.OFFICE.2013.RT.RTM.WOA.ENGLISH.DVD-WZT
MICROSOFT.WINDOWS.RT.8.1.ADK.KIT.WOA.RTM-WZT
Thats all I want to say
Click to expand...
Click to collapse
Anyone tried it yet? Looks like a risky process.

windowsrtc said:
MICROSOFT.WINDOWS.RT.8.1.WITH.OFFICE.2013.RT.RTM.WOA.ENGLISH.DVD-WZT
MICROSOFT.WINDOWS.RT.8.1.ADK.KIT.WOA.RTM-WZT
Thats all I want to say
Click to expand...
Click to collapse
Thanks. Unfortunately, what I gather from what I'm reading is that that image does not contain drivers. You need to manually add the drivers to the image before you install. If you don't, you'll brick your tablet, according to WZT. People may want wait a little bit until there are clear directions and a few people who can verify that they worked (i.e. that they installed 8.1 without any problems).
Additional note: It sounds like the driver package is only for the Surface RT, so users with other Windows RT tablets (ex. ASUS VivoTab RT) may brick their tablets if they try to use it. They'll have to wait until someone releases a driver package for their model (which WZT says might have to be taken from the Preview build).

Osprey00 said:
Even more unfortunately, while WZT has teased info about the driver package, they haven't actually leaked it yet.
Click to expand...
Click to collapse
This part isn't actually true, for what it's worth- it's included with the main download.

jhoff80 said:
This part isn't actually true, for what it's worth- it's included with the main download.
Click to expand...
Click to collapse
Oh, OK. I didn't catch that. They made it appear as though it was a separate download. Ah, you're right: there they are.

just run setup.exe
all drivers for surface are build in
BTW:I have rollback to 8.0 again

Osprey00 said:
...users with other Windows RT tablets (ex. ASUS VivoTab RT) may brick their tablets if they try to use it.
Click to expand...
Click to collapse
It is very difficult to brick an RT device. You can always recover it if you can boot to USB, and you have a recovery image and familiar with windows command line tools (diskpart, dism and so on).
Unfortunatley I'm on a business trip and can't create an upgrade instruction for VivoTab users. But there is nothing difficult - as we already have all needed drivers on a recovery partition, and all you need - just insert them into WIM using the Wzor's instructions from his original post on ru-board.

Installed this tonight. Note that drivers are NOT included in the iso from Wzor.
Extract boot.wim and install.wim from Wzor's iso, inject Wzor's RTM drivers via dism, commit, put boot.wim and install.wim with drivers back into iso, image to USB drive. I installed from within RT using setup (keeping nothing).
You have to use the default key on installation. You need to find out your actual RT key before you do this otherwise you end up with a non-activated RT 8.1 and no key. Export DigitalProductId and DigitalProductId4 from HKLM\SOFTWARE\Microsoft\Windows NT\CurrentVersion and obtain your key. Instructions on how to here.
Works great. In the short amount of time I've been testing everything works perfectly OK, including all my accessories. (discussion here).

mamaich said:
It is very difficult to brick an RT device. You can always recover it if you can boot to USB, and you have a recovery image and familiar with windows command line tools (diskpart, dism and so on).
Click to expand...
Click to collapse
I figured as much, but not everyone may have the recovery image or the knowledge, and, for them, a dead device that they're unable to recover is as good as a brick. Regardless, I just wanted to pass along the same language that WZT used so that I'm not guilty of misrepresenting the risks or responsible if someone can't fix what he got himself into.
derausgewanderte said:
Installed this tonight. Note that drivers are NOT included in the iso from Wzor.
Extract boot.wim and install.wim from Wzor's iso, inject Wzor's RTM drivers via dism, commit, put boot.wim and install.wim with drivers back into iso, image to USB drive. I installed from within RT using setup (keeping nothing).
You have to use the default key on installation. You need to find out your actual RT key before you do this otherwise you end up with a non-activated RT 8.1 and no key. Export DigitalProductId and DigitalProductId4 from HKLM\SOFTWARE\Microsoft\Windows NT\CurrentVersion and obtain your key. Instructions on how to here.
Works great. In the short amount of time I've been testing everything works perfectly OK, including all my accessories. (discussion here).
Click to expand...
Click to collapse
Thanks for your instructions and verifying that it works. The original instructions don't mention writing down your current key first. While I likely would've done that anyways, it's re-assuring to see it in writing, just in case. I might give this a go tomorrow.

FYI, there's now an ISO with the Surface RT drivers baked in, so that users don't have to use DISM to add them manually. The release name is:
DRIVERS FOR SURFACE RT ONLY___MICROSOFT WINDOWS RT 8 1 WITH OFFICE 2013 RT RTM WOA ENGLISH DVD-WZT
Note that it's only for the Surface RT, not other RT tablets.
Also note that you need the installation key, and, also, before installation, you need to export and decrypt your retail 8.0 key. Information on that is available here

Osprey00 said:
Also note that you need the installation key, and, also, before installation, you need to export and decrypt your retail 8.0 key. Information on that is available here
Click to expand...
Click to collapse
and here is the direct link to Osprey00's post with a way of getting the key if you only have your RT.

Good news!
I'll just wait till some skillful surface owner gets the jailbreak and then update!

huslterose said:
Good news!
I'll just wait till some skillful surface owner gets the jailbreak and then update!
Click to expand...
Click to collapse
[EDIT: Never mind. I misunderstood.]
I don't follow. There's nothing to "jailbreak" and it can't get much easier than it is now (outside of simply waiting until Microsoft rolls out 8.1 via Automatic Updates). You just follow instructions to find out your 8.0 key, install the 8.1+drivers ISO (not the one in the OP; the one that I listed a few posts up) with a general installation key, then activate 8.1 with your 8.0 key.

Osprey00 said:
I don't follow. There's nothing to "jailbreak" and it can't get much easier than it is now (outside of simply waiting until Microsoft rolls out 8.1 via Automatic Updates). You just follow instructions to find out your 8.0 key, install the 8.1+drivers ISO (not the one in the OP; the one that I listed a few posts up) with a general installation key, then activate 8.1 with your 8.0 key.
Click to expand...
Click to collapse
I think he is referring to the lack of jailbreak on 8.1 for unsigned desktop apps - a feature which should have been in the OS from the start, instead microsoft wasted time patching the exploit the jailbreak used and destroyed the usefulness of the tablet for some.
He was probably intending to say something along the lines of him not updating to 8.1 until after someone makes a new jailbreak for it.
If you can live without the jailbreak, thats fine. Windows store is a bit too limited in my opinion, but it will grow (still gutted they blocked access to both localhost for network connections and COM ports in windows apps though).

SixSixSevenSeven said:
I think he is referring to the lack of jailbreak on 8.1 for unsigned desktop apps - a feature which should have been in the OS from the start, instead microsoft wasted time patching the exploit the jailbreak used and destroyed the usefulness of the tablet for some.
He was probably intending to say something along the lines of him not updating to 8.1 until after someone makes a new jailbreak for it.
If you can live without the jailbreak, thats fine. Windows store is a bit too limited in my opinion, but it will grow (still gutted they blocked access to both localhost for network connections and COM ports in windows apps though).
Click to expand...
Click to collapse
Ah! Gotcha. It slipped my mind that the jailbreak for unsigned apps not working in 8.1 is a valid reason for not upgrading, so I was thinking that he was waiting for something to make the upgrade, itself, even easier. Thanks for the clarification.

@Osprey00 - is there a direct link perhaps

aooga said:
Could someone please post instructions on how to decrypt the registry values? The link that was posted is down. Thanks.
Click to expand...
Click to collapse
Sure. There are a few different ways to do it. In order of simplest to most complicated...
METHOD 1 - Can be done solely from Windows RT (any version):
1. Follow these instructions to create a batch file.
2. Run the batch file on the tablet to get your key.
3. Either write the key down or right-click anywhere in the window, select Mark, highlight the key, right-click again (which will copy the key to the clipboard), paste the key into a text file and then copy that text file to another computer or backup drive.
4. Optional, but recommended: Check that the key is valid by inputting it into a key checker, such as The Ultimate PID Checker. If it tells you that the key is invalid, then try one of the other two methods.
METHOD 2 - Requires regular, non-RT Windows (XP/Vista/7/8):
1. In RT, open the charms bar, click Search, enter "Regedit" and run Regedit.
2. Export HKEY_LOCAL_MACHINE\Software\Microsoft\Windows NT\CurrentVersion to a .reg file.
3. Copy that .reg file to your non-RT Windows.
4. On your non-RT Windows (all remaining steps will be done there), right-click the .reg file and choose Edit. Change "CurrentVersion" to "CurrentVersionRT". Re-save the file.
5. Double-click on the .reg file and import it.
6. Download and install WinTK.
7. Run WinTK, paste "HKEY_LOCAL_MACHINE\Software\Microsoft\Windows NT\CurrentVersionRT" (without quotes) into the field and press the Decrypt button.
*If, for some reason, WinTK won't run, you can try this: download and unzip Produkey, run Regedit, export your CurrentVersion key to a backup .reg file, change the key name in your RT .reg file from "CurrentVersionRT" back to "CurrentVersion", remove all values in your RT .reg file except for DigitalProductId and DigitalProductId4 (make sure that they're NOT the ones under the DefaultProductKey sub-branch), import that (thus overwriting your Windows key with your Windows RT key), run Produkey, write down the Product Key, then import the backup .reg file to restore your Windows key (important, obviously).
8. Write down the product key.
9. Optional, but recommended: Check that the key is valid by inputting it into a key checker, such as The Ultimate PID Checker. If it tells you that the key is invalid, then try one of the other two methods.
10. Optional: Open Regedit again and delete the CurrentVersionRT key, just to clean up.
METHOD 3 - Can be done solely from Windows RT, but only on 8.0 (won't work on 8.1 Preview or 8.1 RTM) and is more complicated than Method 1:
1. Download and unzip the RT jailbreak tool.
2. Run RunExploit.bat. Choose 'R' from the menu. Let it finish, then press any key when it asks you to.
3. Download and install Win86emu.
4. Download and unzip Produkey.
5. Open the charms bar, click Search, enter "Regedit" and run Regedit.
6. Export HKEY_LOCAL_MACHINE\Software\Microsoft\Windows NT\CurrentVersion to a .reg file.
7. Find the Win86emu tile (icon is "x86") on your Start screen, flick down on it to bring up the options bar and tap Open File Location... or, at the Desktop, you can browse to C:\ProgramData\Microsoft\Windows\StartMenu\Programs\win86emu.
8. Double-tap the "x86 Registry Editor" shortcut.
9. In that registry editor, import the .reg file that you exported in step 4. This will import the settings into the special x86 registry that the emulator created when you installed it and which all x86 programs (including Produkey) will think is the real registry.
10. Double-tap the "Run x86 Program" shortcut.
11. Browse to and select the produkey.exe that you unzipped in step 2.
12. Find the Product Key listed for Windows in the window that appears and write it down. If nothing appears, click on Select Source and verify that it's searching the local computer (top-most radio button).
13. Optional, but recommended: Check that the key is valid by inputting it into a key checker, such as The Ultimate PID Checker. If it tells you that the key is invalid, then try one of the other two methods.
If one method doesn't seem to work for you, try one of the others.

Osprey00 said:
Sure. There are a few different ways to do it. I'll describe two...
...
Hopefully, I didn't forget any steps from either of those methods.
Click to expand...
Click to collapse
Thanks!. Now just waiting to download the iso. Its taking an age.
EDIT: mydigitallife was hacked...thats why the links are down.

aooga said:
Thanks!. Now just waiting to download the iso. Its taking an age.
EDIT: mydigitallife was hacked...thats why the links are down.
Click to expand...
Click to collapse
thanks for the info. was about to search for reasons. hacked by MS?

derausgewanderte said:
thanks for the info. was about to search for reasons. hacked by MS?
Click to expand...
Click to collapse
Yeah I was clueless why it wasn't working, so I just looked at their facebook page.
Would putting a link like this on XDA be considered warez? If not, can someone who has already downloaded the ISO with drivers upload it somewhere? There is no way I'm waiting till Oct. 16

[GUIDE] Install Windows 10 mobile on a Nokia Lumia 530 (post-discontinuation friendly)

While the Nokia Lumia 530 isn’t officially supported, it’s still possible to get Windows 10 mobile running on it. At the time of writing, it has become a bit tricky to get it to work, since most official Microsoft tools are discontinued and will therefore not work. I will be linking the files which I’ve used. The credits to the people who made or shared the tools and guides I used will be at the bottom of this guide.
Note that I am not responsible for any damage made. Proceed at your own risk!
Prerequisites:
- A Nokia Lumia 530 running the Windows 8.1 Denim Update (will be referred to as "device")
- A stable Windows 7 system or VM, with .NET Framework 4.5.x or 4.6.x (on Windows 10, the IUTool will fail to synchronize, hence this requirement)
- An internet connection that can handle a download of approximately 2GB data on the computer and about the same on the phone
- A good USB cable (a flimsy one with a loose fit could brick the device while it’s updating)
- The programs linked below
First part of the installation:
1. Make sure the device is fully charged. If it’s not fully charged the device could get (soft-)bricked.
2. Factory reset the device, so you have as much storage as possible available on the device. After the reset is done, leave it at the language selection screen, because it doesn’t do anything there.
3. Extract HCTSW_WXMSOUP_V5.3beta6.update.lzma2.7z with 7zip or whatever you prefer.
4. Download the Visual C++ libraries from here: https://www.techpowerup.com/download/visual-c-redistributable-runtime-package-all-in-one/ and run the install script.
5. The next thing you are going to do is download the updates, push them to the device and install them. This will take some time, but it depends on your internet connection for the most part. The files will be downloaded from the official Microsoft servers. Now here’s what to do: open run_en.cmd and follow the steps. These are pretty clear, so I don’t think I need to point all of them out here. It will open a webpage where you can download WDRT, you will need to install that for the tool to work.
6. Now you can move on to the second part.
Second part of the installation:
In this part of the installation, you will be updating the device from version 1511 to the latest available build, which should have a working Microsoft store.
1. The setup of the device. The version that just got installed doesn’t have a lot of options yet, including language packs. If you have a device that’s not English United States, the keyboard will bug out on setup, because it’s trying to access a language pack that doesn’t exist. Therefore, the first step, setting the language should be English (United States), so the OS itself won’t bug out. Once you’ve set the language (it will prompt to reboot, do that), you can go through the rest of the setup. Don’t log it into your Wi-Fi, don’t log it into your Microsoft account and don’t turn on automatic app updates. It’ll say it needs to set up apps, that takes some time but eventually you’ll get to the home screen. Now is when you need a few tools, which brings us to step 2.
Now is a good moment for me to point out that, if you have a non-English-US device, the keyboard for another language is still "installed". It can be removed by holding it in settings -> time and language -> keyboard and choosing “Delete”.
2. Installing Interop Tools. In order to get updates, you’ll need to modify your device a bit. This won’t be very hard, but it involves some registry modifications so you’ll have to pay close attention.
Go to settings -> update and security -> for developers and enable developer mode, so you can sideload the Interop Tools (Linked below). Copy the contents of the Interop Tools zip to the device first. Then, go to the file manager on the phone and go to the directory where you put the files. INSTALL THE DEPENDENCIES IN THE \ARM FOLDER FIRST, THEN THE INTEROP TOOLS FILE ITSELF! Check if the Interop Tools installed on the “all apps screen” and get ready to open it.
3. Modifying the registry. Open Interop Tools and tap the “This Device” button. This will bring up a menu.
3.1. Tap the menu button on the top left corner, then select “Modify Registry”. In the “Registry Key Path”, put SYSTEM\Platform\DeviceTargetingInfo. Then, put PhoneManufacturerModelName in the “Registry Value Name” box and tap the “Read” button at the bottom. You’ll see some text appear in a box. This will need to be edited to the following value: RM-1089_1048. After you did that, tap the “Write” button.
3.2. Now put PhoneModelName in the the “Registry Value Name” box and tap “Read” again. Now change the value to Lumia 535 and tap “Write”.
3.3. Exit out of Interop Tools and go to the next step.
4. Logging in to the Wi-Fi and checking for updates.
4.1. Logging it in to the Wi-Fi. Go to settings -> network & wireless -> Wi-Fi and choose your network. Easy peasy probably.
4.2. Checking for updates. This is the part that always went wrong with me, because of storage limits (gotta love that 4GB eMMC). But if I’ve explained this well enough, you might not have to do a lot of weird stuff. Oh well, to the instruction we go. Go to settings -> update and security -> windows update and check for updates. This will take a while! Keep it on wall power because updating can only be done at 40% or more at this point. I got two updates: from 1511 to early 1607 and from that to late 1607. Maybe you can get a newer version with WDRT or OTC but I doubt that to be honest.
Hooray! Now you should have a fully functional Nokia Lumia 530 with Windows 10 mobile!
Credits:
nemesis from Realmtech (for the registry changes) (https://www.realmtech.net/user/1)
@hikari_calyx (for the semi-offline update tool)
@STALKER18 (for the tips on how to clear storage)
@gus33000 (for the Interop Tools)
My dad (for the device)
Everyone who encouraged me to do this mod
Files:
Interop Tools: https://forum.xda-developers.com/attachments/interoptools_rc2_1-9-400-0_arm-zip.3995811/
And it's dependencies: https://forum.xda-developers.com/attachments/dependencies_arm-zip.3995814/
Windows 10 mobile semi-offline updater: https://forum.xda-developers.com/attachments/hctsw_wxmsoup_v5-3beta6-update-lzma2-7z.4955261/
PS: If you brick the device, the WDRT can restore it. If it just puts it in flashing mode, you can use Windows Phone Internals to download and flash a ROM. That tool can be found here: https://www.wpinternals.net/index.php/downloads/doc_download/46-wpinternals-2-8-zip

[ADDITION] Updating from build 1607 to 1709.
I said it wouldn’t be possible and it would break stuff, but I tried it and it doesn’t break anything some people say it might break. Yeah, it might impact on battery life a bit, but nothing has broken for me (yet), it has only improved.
I’ve learned that the update from 1607 to 1703 is the hardest one yet, but you should be able to get it going. This is because the preinstalled Store in 1607 can connect to the app update servers, but it can’t view the app. This is a difficult situation because many apps will become very large when they get updated. You need to figure out for yourself what gets you the space you need, but I found that uninstalling all the apps that can be uninstalled and deleting system apps through MTP (which can be done by bootloader unlocking, rooting and booting into mass storage mode with Windows Phone Internals (I recommend that you only delete OneNote, SkyDrive (as it’s being referred to in /data/program files/windowsapps) and the Xbox app).
Step 0: you might want to factory reset first
Let’s get to the updating though…
1. Modifying the registry. Open Interop Tools and tap the “This Device” button. This will bring up a menu.
1.1. Tap the menu button on the top left corner, then select “Modify Registry”. In the “Registry Key Path”, put SYSTEM\Platform\DeviceTargetingInfo. Now do the exact same as you did before, except use these “registry value names” and put the corresponding information into the box below that. Don’t forget to tap write!
Values you should use:
PhoneHardwareVariantRM-1104PhoneManufacturerMicrosoftMDGPhoneManufacturerModelNameRM-1104_11210PhoneModelNameLumia 950
1.2. Exit out of Interop Tools and go to the next step.
2. Logging in to the Wi-Fi and checking for updates.
2.1. Logging it in to the Wi-Fi. Go to settings -> network & wireless -> Wi-Fi and choose your network. Easy peasy probably.
2.2. Checking for updates. Go to settings -> update and security -> Windows Update and check for updates. This will take a while! Keep it on wall power because updating can only be done at 40% or more at this point. I got 3 updates, one from 1607 to 1703, one from 1703 to 1709 and another one from old 1709 to last 1709.
Credit to @demon2112 for the registry values

Can you backup your efiesp.bin partition and share?

augustinionut said:
Can you backup your efiesp.bin partition and share?
Click to expand...
Click to collapse
Did you break it?
Edit: WPInternals refuses to put the phone in mass storage mode so uh... Yeah...

I managed to get them off with Interop Tools

How?

augustinionut said:
How?
Click to expand...
Click to collapse
In the Interop Unlock menu, there's a mount entire storage option. Copied the EFIESP from there and compiled it into a bin. For WPI the Windows on the phone is too new :/

Thats why didnt worked
I wanted dumped partition with, WPInternals.

augustinionut said:
Thats why didnt worked
I wanted dumped partition with, WPInternals.
Click to expand...
Click to collapse
Yeah that doesn't work. Rename the .bin to .zip, extract, mount the phone in mass storage mode and copy the files to the EFIESP folder/symlink. If you can't do that, WDRT can probably unbreak it

Please anounce me when you can upload the dumped partition.

Is resulting that efiesp.bin , data.bin and mainos.bin are related, so i cant upgrade my phone to windows 10 mobile without them.

augustinionut said:
Is resulting that efiesp.bin , data.bin and mainos.bin are related, so i cant upgrade my phone to windows 10 mobile without them.
Click to expand...
Click to collapse
Just flash the original FFU. Literally all I did is in the guide and I never had to flash something from another device

Thanks, but: my phone was reflashed with reset protection active. Guess what?

augustinionut said:
Thanks, but: my phone was reflashed with reset protection active. Guess what?
Click to expand...
Click to collapse
Something that might work (according to a friend. Again, I am not responsible for a phone that gets rendered useless)
Mount as mass storage, diskpart clean the thing, hold power button for ~10 seconds, flash a bootloader with WDRT (may fail 2-3 times), flash FFU

_Yep, erase clean DPP partition )) buhahahaha

How do you get to the Denim update? I'm getting the error that I am running a build older than 8.10.14219.341 and need to update first.

EirikrHinnRauthi said:
How do you get to the Denim update? I'm getting the error that I am running a build older than 8.10.14219.341 and need to update first.
Click to expand...
Click to collapse
You can download and flash it in WPInternals (will delete all data so back that up first) or WDRT (not sure if that erases userdata)

BennoMP said:
You can download and flash it in WPInternals (will delete all data so back that up first) or WDRT (not sure if that erases userdata)
Click to expand...
Click to collapse
WDRT already says I'm at the latest version of Windows for my device, so that sucks. I shall try WPInternals! Thanks!

Would you please transfer a video of the process?
BennoMP said:
While the Nokia Lumia 530 isn’t officially supported, it’s still possible to get Windows 10 mobile running on it. At the time of writing, it has become a bit tricky to get it to work, since most official Microsoft tools are discontinued and will therefore not work. I will be linking the files which I’ve used. The credits to the people who made or shared the tools and guides I used will be at the bottom of this guide.
Note that I am not responsible for any damage made. Proceed at your own risk!
Prerequisites:
- A Nokia Lumia 530 running the Windows 8.1 Denim Update (will be referred to as "device")
- A stable Windows 7 system or VM, with .NET Framework 4.5.x or 4.6.x (on Windows 10, the IUTool will fail to synchronize, hence this requirement)
- An internet connection that can handle a download of approximately 2GB data on the computer and about the same on the phone
- A good USB cable (a flimsy one with a loose fit could brick the device while it’s updating)
- The programs linked below
First part of the installation:
1. Make sure the device is fully charged. If it’s not fully charged the device could get (soft-)bricked.
2. Factory reset the device, so you have as much storage as possible available on the device. After the reset is done, leave it at the language selection screen, because it doesn’t do anything there.
3. Extract HCTSW_WXMSOUP_V5.3beta6.update.lzma2.7z with 7zip or whatever you prefer.
4. Download the Visual C++ libraries from here: https://www.techpowerup.com/download/visual-c-redistributable-runtime-package-all-in-one/ and run the install script.
5. The next thing you are going to do is download the updates, push them to the device and install them. This will take some time, but it depends on your internet connection for the most part. The files will be downloaded from the official Microsoft servers. Now here’s what to do: open run_en.cmd and follow the steps. These are pretty clear, so I don’t think I need to point all of them out here. It will open a webpage where you can download WDRT, you will need to install that for the tool to work.
6. Now you can move on to the second part.
Second part of the installation:
In this part of the installation, you will be updating the device from version 1511 to the latest available build, which should have a working Microsoft store.
1. The setup of the device. The version that just got installed doesn’t have a lot of options yet, including language packs. If you have a device that’s not English United States, the keyboard will bug out on setup, because it’s trying to access a language pack that doesn’t exist. Therefore, the first step, setting the language should be English (United States), so the OS itself won’t bug out. Once you’ve set the language (it will prompt to reboot, do that), you can go through the rest of the setup. Don’t log it into your Wi-Fi, don’t log it into your Microsoft account and don’t turn on automatic app updates. It’ll say it needs to set up apps, that takes some time but eventually you’ll get to the home screen. Now is when you need a few tools, which brings us to step 2.
Now is a good moment for me to point out that, if you have a non-English-US device, the keyboard for another language is still "installed". It can be removed by holding it in settings -> time and language -> keyboard and choosing “Delete”.
2. Installing Interop Tools. In order to get updates, you’ll need to modify your device a bit. This won’t be very hard, but it involves some registry modifications so you’ll have to pay close attention.
Go to settings -> update and security -> for developers and enable developer mode, so you can sideload the Interop Tools (Linked below). Copy the contents of the Interop Tools zip to the device first. Then, go to the file manager on the phone and go to the directory where you put the files. INSTALL THE DEPENDENCIES IN THE \ARM FOLDER FIRST, THEN THE INTEROP TOOLS FILE ITSELF! Check if the Interop Tools installed on the “all apps screen” and get ready to open it.
3. Modifying the registry. Open Interop Tools and tap the “This Device” button. This will bring up a menu.
3.1. Tap the menu button on the top left corner, then select “Modify Registry”. In the “Registry Key Path”, put SYSTEM\Platform\DeviceTargetingInfo. Then, put PhoneManufacturerModelName in the “Registry Value Name” box and tap the “Read” button at the bottom. You’ll see some text appear in a box. This will need to be edited to the following value: RM-1089_1048. After you did that, tap the “Write” button.
3.2. Now put PhoneModelName in the the “Registry Value Name” box and tap “Read” again. Now change the value to Lumia 535 and tap “Write”.
3.3. Exit out of Interop Tools and go to the next step.
4. Logging in to the Wi-Fi and checking for updates.
4.1. Logging it in to the Wi-Fi. Go to settings -> network & wireless -> Wi-Fi and choose your network. Easy peasy probably.
4.2. Checking for updates. This is the part that always went wrong with me, because of storage limits (gotta love that 4GB eMMC). But if I’ve explained this well enough, you might not have to do a lot of weird stuff. Oh well, to the instruction we go. Go to settings -> update and security -> windows update and check for updates. This will take a while! Keep it on wall power because updating can only be done at 40% or more at this point. I got two updates: from 1511 to early 1607 and from that to late 1607. Maybe you can get a newer version with WDRT or OTC but I doubt that to be honest.
Hooray! Now you should have a fully functional Nokia Lumia 530 with Windows 10 mobile!
Credits:
nemesis from Realmtech (for the registry changes) (https://www.realmtech.net/user/1)
@hikari_calyx (for the semi-offline update tool)
@STALKER18 (for the tips on how to clear storage)
@gus33000 (for the Interop Tools)
My dad (for the device)
Everyone who encouraged me to do this mod
Files:
Interop Tools: https://forum.xda-developers.com/attachments/interoptools_rc2_1-9-400-0_arm-zip.3995811/
And it's dependencies: https://forum.xda-developers.com/attachments/dependencies_arm-zip.3995814/
Windows 10 mobile semi-offline updater: https://forum.xda-developers.com/attachments/hctsw_wxmsoup_v5-3beta6-update-lzma2-7z.4955261/
PS: If you brick the device, the WDRT can restore it. If it just puts it in flashing mode, you can use Windows Phone Internals to download and flash a ROM. That tool can be found here: https://www.wpinternals.net/index.php/downloads/doc_download/46-wpinternals-2-8-zip
Click to expand...
Click to collapse

Hello! I followed your step with editing values and after checking updates, there was an update which is Windows 10 Mobile (10.0.14393.1066) as of now, May 2022.
my question is what is the size of this update? and will I able to install this with my Lumia 530?
any other way to install this offline? i really need this update because I need working Microsoft Store.
Thanks...