Windows 10 on Surface RT : additional apps + WPF support - Windows RT General

Thanks to the help of this forum, I have successfully installed Windows 10 on my Tablet Surface RT 1.
I was wondering 1) if there were additional applications to install somewhere else than the store and 2) how to get support of WPF (which appears not to be the case by default).
Below some of my findings.
Installation of recompiled applications
On page https://forum.xda-developers.com/showthread.php?t=2092348, GoodDayToDie did the great job of collecting several apps recompiled for Windows RT (work done between 2013 and 2015). I tried Notepad++, but I encountered a "missing DLL" error.
I solved this issue by installing vcredist_arm.exe from https://www.microsoft.com/en-US/download/details.aspx?id=30679
It contains the C libraries used by the cross-compilation process. I have made Notepad++ and prboom (a Doom equivalent) to work. Qupzilla (browser) also technically works but does not support https, so makes it pretty useless.
Support of WPF
The Windows 10 ARM version apparently does not support WPF. I tried the procedure described on page https://forum.xda-developers.com/windows-8-rt/rt-development/wpf-windows-rt-devices-t3763345 and it worked !
Thanks a lot @black_blob !
Some tips:
* The 7z file containing the DLLs and the instructions is in the "downloads" tab of the page
* Just follow the instructions located in the "notes.txt" file. There was no file already existing on the Windows 10 ARM version when I did the copy of the files.
* I have disabled hardware acceleration as described in the instructions, because the forms of my test application were blank.
=> I had to take ownership of the Avalon.Graphics Registry node, and to give the rights to my account before being able to add the DisableHWAcceleration registry key.
You can now write C# WPF applications targeting .NET 4.5, they will work (unless you use unsupported references) !
As an example, have a look on the image attached. It shows sample apps from https://github.com/microsoft/InteractiveDataDisplay.WPF. I just compiled the code on a standard PC and then moved and run the binaries on the tablet.

Hi. I need help on disabling secure boot. i tried downgrading it ti 8.0, i managed to unlock bitlocker but still I cant disable secureboot. the secureboot file only shows F3 options. is there any fix into this? thanks

I tried this 3 months ago but I realized not all compiled programs for WPF work, but it's still great.

Related

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.

[Q] newbie help with framework and cab files

Hello xda developers...
First-time poster.
Advanced Beginner/Intermediate programmer attempting first Windows Mobile app.
Got a deal on a t-mobile dash off ebay and am trying to create an application or two for it for personal use.
Problem: Getting a simple program written in c# to run on a t-mobile dash.
Question: How does one create a .cab file?
I've been doing research online and windows website doesn't mention .cab at all. Some discussions i've found said it's impossible. confused.
Back Story:
The Test Application: a text box, listbox and two buttons (one adds entry in text box to list box. the other button clears items from list).
Running Visual Studio 2008 on Vista (business? not the stunted home version).
Programming in C#. For a T-Mobile Dash (HTC Excalibur?)... running windows mobile 6.x.
I coded a simple app just to see if I could get something functioning on my phone. The emulator was windows 5 (which seemed okay. all 3rd-party apps i've used are windows 5. work fine).
App ran fine in emulator; however, when I copied the .exe to phone and ran, it said the framework was too new (which seemed odd going from windows mobile 5 emulation to windows mobile 6 os).
IS root problem from .exe file (where I need .cab?)
Any advice, website links or anything would be gratefully appreciated.
Thanks all!
First of all what version of the .NET CF framework is running on the real device?
Run \WINDOWS\CGACUTIL.EXE
A popup window reports which version(s) are installed.
This is of the form [Major.Minor.Build.0]
Eg [2.0.7045.0] is .NET CF 2.0 and [3.5.9198.0] is .NET CF 3.5
If the version of .NET CF for which you have built the app, is the same as that on the device, the exe should run fine. You do not need a cab, copy the release .exe straight to the device.
Otherwise, there are two options,
1) Install the .NET CF version required on the device.
2) Change the .NET CF in the VS2008 build. This is not always easy as it it is usually selected when you create the project. See attached.
2a) It might be easier creating a new project against the correct .NET CF and the copy the old source files over.
If it lets you change the framework, you will find it in the Application side tab of the Properties of your project, (Project, not Solution). If the "Target Framework:" drop down box is greyed out, see the second image, you are stuck with 2a) above.

[Q] Mod Windows RT to enable Remote Desktop

In the past, Windows has had editions for consumers that did not include Remote Desktop enabled. Usually there was a patch to enable it. Recently it has been proved how there is almost no difference between Windows 8 and Windows RT and that RT is just a port of Windows 8. So what about all the system files? They can be changed just like x86 Windows. So what about enabling Remote Desktop, so we don't need a ARM remote app that we need to unlock Windows for, and we can use what comes with Windows. In the past we modified the termsrv.dll file and changed some registry settings. I've included the Windows 8 and the Windows RT versions of termsrv.dll so that maybe some clever ones might try and crack a solution to enabling it on Windows RT.
sionicion said:
In the past, Windows has had editions for consumers that did not include Remote Desktop enabled. Usually there was a patch to enable it. Recently it has been proved how there is almost no difference between Windows 8 and Windows RT and that RT is just a port of Windows 8. So what about all the system files? They can be changed just like x86 Windows. So what about enabling Remote Desktop, so we don't need a ARM remote app that we need to unlock Windows for, and we can use what comes with Windows. In the past we modified the termsrv.dll file and changed some registry settings. I've included the Windows 8 and the Windows RT versions of termsrv.dll so that maybe some clever ones might try and crack a solution to enabling it on Windows RT.
Click to expand...
Click to collapse
termsrv is a system service and how can we use a modified termsrv.dll before we use the Jailbreak tool?maybe we can edit termsrv.dll in the memory.
We can't, I suspect. Even after jailbreaking, the lack of a signature on a system file may be a problem. It's worth a shot, though.
termsrv.dll -should- be a usermode library that would be editable after the jailbreak.
I am able to take ownership of the file and replace it. But it won't use the termsrv.dll from my windows 8… I'm almost positive it is because the dll is different depending on architecture. But it should be as easily replaceable as any system file on windows 8, am I right? I don't see why it wouldn't but I could be wrong.
Yeah, pretty much. You definitely won't be able to use the Win8 version (x86 machine code, ARM processor, not gonna fly...) but a modified version of the Windows RT version might work. Bear in mind that since modifying the DLL will invalidate the signature, this won't work if the signature validation is enforced (i.e. you'll have to jailbreak).
Should be possible using the Remote Debugging Tools or, even better, cdb. Put it in a .cmd file in autorun and voila
clrokr said:
Should be possible using the Remote Debugging Tools or, even better, cdb. Put it in a .cmd file in autorun and voila
Click to expand...
Click to collapse
Please!! Remote desktop would be awesome enabled on the Surface RT, if someone could work on it I know a lot of people would be very grateful!
I've already posted a method that should enable RDP here: http://forum.xda-developers.com/showpost.php?p=36386089&postcount=211 - no need to patch DLL, and would work on an a locked device. But you'll have to manually edit binary registry value, instead of using a provided tool.
I have not tested RDP, but after using this method I was able to recover an option of joining device to Active Directory domain (it was blocked by the similar policies).
mamaich said:
I've already posted a method that should enable RDP here: http://forum.xda-developers.com/showpost.php?p=36386089&postcount=211 - no need to patch DLL, and would work on an a locked device. But you'll have to manually edit binary registry value, instead of using a provided tool.
I have not tested RDP, but after using this method I was able to recover an option of joining device to Active Directory domain (it was blocked by the similar policies).
Click to expand...
Click to collapse
Can you share how you managed to get the rt joined to a domain?
mamaich said:
I've already posted a method that should enable RDP here: http://forum.xda-developers.com/showpost.php?p=36386089&postcount=211 - no need to patch DLL, and would work on an a locked device. But you'll have to manually edit binary registry value, instead of using a provided tool.
I have not tested RDP, but after using this method I was able to recover an option of joining device to Active Directory domain (it was blocked by the similar policies).
Click to expand...
Click to collapse
Wouldn't both methods work though? Your method works by enabling features from other editions by telling Windows that's what edition it is running. It disables it when the Software Protection service restores it to the original template according to the edition. By patching the DLL file, you could trigger Remote Desktop to work without it needing to check in with the kernel policies.
I mean unless you have a way to modify these policies without all the extra occuring, it would work. But Bitlocker and the Software Protection service getting involved...it just sounds like a lot of extra work for something much bigger in the end, and I know there must be an easier way to force Remote Desktop to work without listening to these policies because it has been done in the past.
mamaich said:
I've already posted a method that should enable RDP here: http://forum.xda-developers.com/showpost.php?p=36386089&postcount=211 - no need to patch DLL, and would work on an a locked device. But you'll have to manually edit binary registry value, instead of using a provided tool.
I have not tested RDP, but after using this method I was able to recover an option of joining device to Active Directory domain (it was blocked by the similar policies).
Click to expand...
Click to collapse
I tried to enable one of the Remote Desktop vars last night, allowRemoteConnections I think it was called, but I didn't get anything from it.
mamaich said:
I've already posted a method that should enable RDP here: http://forum.xda-developers.com/showpost.php?p=36386089&postcount=211 - no need to patch DLL, and would work on an a locked device. But you'll have to manually edit binary registry value, instead of using a provided tool.
I have not tested RDP, but after using this method I was able to recover an option of joining device to Active Directory domain (it was blocked by the similar policies).
Click to expand...
Click to collapse
Again, please if you were able to join an RT to the domain. Please let me know what you did. Would love to not get prompted to log in into PowerShell.
apatcas said:
Again, please if you were able to join an RT to the domain. Please let me know what you did. Would love to not get prompted to log in into PowerShell.
Click to expand...
Click to collapse
As I've already wrote - use this method: http://forum.xda-developers.com/showpost.php?p=36386089&postcount=211
1. Edit registry:
Code:
HKEY_LOCAL_MACHINE\SYSTEM\Setup
SetupType=1
CmdLine="cmd.exe"
and reboot. You will enter the setup mode. You would not see the mouse cursor in this mode, and you'll need a hardware keyboard.
2. Open this reg_binary value: HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\ProductOptions\ProductPolicy. Look for unicode string "WorkstationService-DomainJoinEnabled", it is near offset 0x4000. Look at this screenshot:
http://imageshack.us/photo/my-images/526/35796208.png/
Select the "00" byte that follows the zero byte after the 64 (64 00 == unicode "d" letter) as you see on the screenshot. Overwrite it with 01. Be careful not to insert a byte, you need to overwrite the existing byte!
3. Rename sppsvc.exe to anything else so that it would not run on boot and reset ProductPolicy ("ren sppsvc.exe sppsvc.bak")
4. Reboot. Now the option to join the domain would be available.
I have not tried to add workstation to domain myself - try that and post here. After adding to domain you may try to rename sppsvc.bak back to sppsvc.exe as otherwise you'll get the "unactivated" Windows RT. I think that this would only remove the add to domain UI, but the RT would be still domain-joined.
I've tried to edit the remote desktop settings keys - this unblocked the corresponding options in the computer settings, but I was unable to connect. Maybe this is due to absence of RDP code in terminal server service - I don't see anyone listening port 3398 though TermServer service is running.
mamaich said:
As I've already wrote - use this method: http://forum.xda-developers.com/showpost.php?p=36386089&postcount=211
1. Edit registry:
Code:
HKEY_LOCAL_MACHINE\SYSTEM\Setup
SetupType=1
CmdLine="cmd.exe"
and reboot. You will enter the setup mode. You would not see the mouse cursor in this mode, and you'll need a hardware keyboard.
2. Open this reg_binary value: HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\ProductOptions\ProductPolicy. Look for unicode string "WorkstationService-DomainJoinEnabled", it is near offset 0x4000. Look at this screenshot:
http://imageshack.us/photo/my-images/526/35796208.png/
Select the "00" byte that follows the zero byte after the 64 (64 00 == unicode "d" letter) as you see on the screenshot. Overwrite it with 01. Be careful not to insert a byte, you need to overwrite the existing byte!
3. Rename sppsvc.exe to anything else so that it would not run on boot and reset ProductPolicy ("ren sppsvc.exe sppsvc.bak")
4. Reboot. Now the option to join the domain would be available.
I have not tried to add workstation to domain myself - try that and post here. After adding to domain you may try to rename sppsvc.bak back to sppsvc.exe as otherwise you'll get the "unactivated" Windows RT. I think that this would only remove the add to domain UI, but the RT would be still domain-joined.
I've tried to edit the remote desktop settings keys - this unblocked the corresponding options in the computer settings, but I was unable to connect. Maybe this is due to absence of RDP code in terminal server service - I don't see anyone listening port 3398 though TermServer service is running.
Click to expand...
Click to collapse
Joined... Nice find.
apatcas said:
Joined... Nice find.
Click to expand...
Click to collapse
Have it remained domain-joined after restoring the original sppsvc.exe?
You have to return it back, otherwise you'll be annoyed with the activation reminders.
mamaich said:
Have it remained domain-joined after restoring the original sppsvc.exe?
You have to return it back, otherwise you'll be annoyed with the activation reminders.
Click to expand...
Click to collapse
We could possibly patch sppsvc to not check, then start the service up after jailbreaking it.
I'm honestly not sure if this would be considered piracy or not, though.
Edit: I used the program to set every value to 1 in setup mode (The latest jailbreak tool works in setup mode), and I didn't see any change for anything dealing with RDP.
Edit 2: Perhaps I shouldn't have set 'Disable' to 1. Regardless, I set it to 0 and the options popped up, but I can't get anything to go. As mamaich stated, I'm not seeing anything listening on port 3389. netstat -a -b on a desktop with it enabled says it's opened by CryptSvc, but I'm not seeing anything with CryptSvc that's not there on the tablet. That could just be netstat guessing which service running under svchost is actually running it, too.
netham45 said:
We could possibly patch sppsvc to not check, then start the service up after jailbreaking it.
I'm honestly not sure if this would be considered piracy or not, though.
Edit: I used the program to set every value to 1 in setup mode (The latest jailbreak tool works in setup mode), and I didn't see any change for anything dealing with RDP.
Edit 2: Perhaps I shouldn't have set 'Disable' to 1. Regardless, I set it to 0 and the options popped up, but I can't get anything to go. As mamaich stated, I'm not seeing anything listening on port 3389. netstat -a -b on a desktop with it enabled says it's opened by CryptSvc, but I'm not seeing anything with CryptSvc that's not there on the tablet. That could just be netstat guessing which service running under svchost is actually running it, too.
Click to expand...
Click to collapse
I think we must hack the dll file.But I find when I edit a byte in the dll,the service was not able to start.
apatcas said:
Joined... Nice find.
Click to expand...
Click to collapse
So is it true? that your device stays domain-joined after you restore sppsvc.exe?
@ Netham45, you could try to open up W81x86 termsrv.dll and go to these hex locations to find out what functions needed patching.
Hashes
File: W81x86\termsrv.dll
CRC-32: 202cd912
MD4: a879d39b8fbcd968b525af05a66aaf2c
MD5: 7a8e1158291cf4c8d8474a2091b9bf6d
SHA-1: e10028b074d24605e05b5e0bafd42f6a93ac01ad
1550F-15520
17428
A1B29
Then go into WinRT termsrv.dll, jump to those functions by name (because offsets will be different between x86 and RT) and Jmp or Nop as needed for WinRT. Afterwords it could be added via CDB / KD on-the-fly.

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] Run Free Hyper-V Server in Desktop Mode

Hi All,
This is my first guide on XDA and this might not be the right topic but it's related. (This is for Advanced users)
I want to start this thread to show how you can use Microsoft's Free Hyper-V Server for more than just "Hyper-V".
I have done tests with Hardware and VMWare Player (V5) with both Hyper-V 2008 R2 & Hyper-V 2012.
System Requirements;
http://en.wikipedia.org/wiki/Hyper-V#System_requirements_and_specifications
And more specifically;
http://en.wikipedia.org/wiki/Hyper-V#Microsoft_Hyper-V_Server
Download a Free copy of Hyper V Server; (It’s free, so no Install key required!)
http://www.microsoft.com/en-us/server-cloud/hyper-v-server/default.aspx (You might need to register)
I have successfully used VMWare Player 5, Version 4 works for Hyper-V 2008 R2 but not 2012.
If you are trying this on hardware directly, you’ll also need to download your system’s drivers (at a minimum the Network Card) and a web browser
. i.e. Chrome downloader from: https://www.google.com/intl/en/chrome/browser/ (Tested to work correctly in Hyper-V Environment) Save these to a USB stick.
Anything else can be downloaded once Hyper-V Server is up and running.
Follow the Hyper-V installation as usual (all defaults)
As a guide; Select Custom Installation, you'll need more than 10GB hard drive size after we add extras, so pick 20GB as a minimum. wait for the re-boot
At this point you'll be asked to set a password and you'll get a command prompt for a user interface.
That's right, Desktop, control panel, Start menu, Metro, Task Bar, System Tray, Internet Explorer are all User interface elements that are removed from this copy of windows.
This is where this [GUIDE] starts to provide non-standard information;
Let's start by Installing your Drivers. (I'm assuming you know how to use the command prompt to change drive letter of your USB drive and launch the driver installer program.)
OR in VMWare case, on the menu select Install VMWare tools. This will not launch automatically, hence you'll need to use the command prompt to change to your CD/DVD Drive and launch the "Setup.exe" for VMware tools.
Now start the installation for Chrome, similar to above.
Now Chrome is running, Close the prompt to select default browser (it's your only browser...)
Sometimes I have found Chrome to crash with a dinput8.dll error (no all websites), Chrome works with this prompt up, but it's nicer to avoid it prompting.
http://www.driverskit.com/dll/dinput8.dll/585.html * We'll get back to this later...
You'll need to be uncompressed the above file, so lets download 7Zip also
http://www.7-zip.org/download.html
Now we need a file manager, since there is no Windows Explorer (or now called explorer) Explorer2 (x2) fits the bill nicely.
http://www.zabkat.com/x2lite.htm * Free Light Version (There are issues with not displaying some files, That because it’s a 32bit application that is not 100% compatible with a 64bit environment), The Pro Version is US$29.95 and is available in 64bit. When you install this, select the option to replace Explorer (note: there is no explorer, so this option allows explorer2 to handle some calls to explorer)
Now download a Start menu, Taskbar “desktop” replacement http://www.emergedesktop.org/* Free and customizable.
- Lets customize the Emerge desktop,
- If not started run “C:\Program Files\Emerge Desktop\emergeCore.exe”
- Lets start by removing menu Items that are broken due to not having a full copy of windows.
-- Settings, Configure Core, Click on emergeLauncher.exe, the press the Cog.
--- Delete “Homepage”
--- Delete “Executable %AppletDIR%\documentation\...”
--- Delete “ Tutorial”
--- Add Type “Live Folder”, Folder “C:\Users\Public\Desktop” (Click Save)
-- Settings, Configure Core, Click on emergeTasks.exe, the press the Cog.
--- Change Icon Size to 16x16 (Click OK)
- Start menu (or right click any where on the desktop) select Desktop Display, right click, Delete.
Now any new program that puts a shortcut in this folder “C:\Users\Public\Desktop” will appear on the launch Task Bar.
For some "Control Panel" replacement options download a GUI for managing some windows features (These projects help to speed up initial configuration;
http://corefig.codeplex.com/ Corefig for Windows Server 2012 Core and Hyper-V Server 2012
https://coreconfig.codeplex.com/ for Windows Server 2008 R2 x64 Core edition
This together with Sconfig can do quite a bit of windows configurations without resorting to the command line.
Ok the dinput8.dll.zip you downloaded earlier, you can un-compress this and put the dll (not the zip) in to the C:\windows\system32 folder.
If you want to make re-starting faster and don't plan on using Hyper-V, lets remove it. (coreconfig I think has this option but the following will always work) In a command prompt window type the following;
start /w ocsetup microsoft-hyper-v /uninstall
(Windows will need to restart a couple of times to do this)
(Optional) Enable a network share (You can use this like a Network file Server now, I don't know if there is a limitation to the number of connections like in desktop versions of windows)
net share /Grant:Administrator,FULL system=c:\
Remote Desktop Concurrent Users limit: 2 (one console, one remote OR two remote) (1 UP on a windows workstation copy)
Enable with from the Sconfig utility..
If you want to run SQL Server (Tested with 2008 R2) you'll need DotNet3.5
In a command prompt window type the following;
DISM /Online /Enable-Feature /FeatureName:NetFx3 /All
I did this as a test a while ago and I think that is all I needed to do and it worked. (I have gotten it to work, so it would be interesting on how much it can be pushed on this platform)
Need Java? Download Java http://java.com/en/download/
Need to use Office Documents?; http://www.libreoffice.org/download
Need FTP Server?; https://filezilla-project.org/download.php?type=server
Need Web Server?; http://mirror.mel.bkb.net.au/pub/apache//httpd/binaries/win32/
Need QEMU support? http://qemu.weilnetz.de/w64/
I used the built in Windows Updates (option 6 on the Sconfig utility) but I also prefer to use: WSUS Offline http://wsusoffline.net/
WSUS will also quickly get you copies of Silver light & C++ run times (or you can find the URL's manually), I find it's best to use both, WSUS Offline for quick offline copies and windows updates for the latest Microsoft has to offer... (I did not say latest & greatest...)
Work in Progress (probably not going to happen without 3rd party work).
Need Sound? (Don’t know of a solution yet…) I saw someone working on this with Server 2012 Core but I did not find the solution or if it would work with hyper-V copy.
Need Direct X? (Don’t know of a solution yet…) I've tried downloading -redist copies, etc but Direct X has been integrated into windows for years and this is the copy it's removed from.
I'd also want to get VMWare Player working or similar for the USB Pass through feature and 3D client support but I'd probably have to use an alternative. (I heard of a USB Driver for windows to share over Ethernet to another copy of windows)
Okay, this is all I have got for now, your thoughts?

Categories

Resources