Hi guys!
Microsoft said this to The Verge recently:
The scenario outlined is not a security vulnerability and does not pose a threat to Windows RT users. The mechanism described is not something the average user could, or reasonably would, leverage, as it requires local access to a system, local administration rights and a debugger in order to work. In addition, the Windows Store is the only supported method for customers to install applications for Windows RT. There are mechanisms in place to scan for security threats and help ensure apps from the Store are legitimate and can be acquired and used with confidence.
We applaud the ingenuity of the folks who worked this out and the hard work they did to document it. We’ll not guarantee these approaches will be there in future releases.
Click to expand...
Click to collapse
So fire up regedit, go to
Code:
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\WindowsUpdate\Auto Update
and set the DWORD AUOptions to 0x00000000.
Only do this if you want to run unsigned apps!
Stay safe!
clrokr
For those who prefer do-it-for-me solutions, with the ability to roll back, have a pair of .REG files. The "Default" one I taken from my Surface before applying this tweak. The "Disabled" one sets the reg value as above.
@clrokr: We gotta get you a RD tag, pronto! You're doing great things.
GoodDayToDie said:
@clrokr: We gotta get you a RD tag, pronto! You're doing great things.
Click to expand...
Click to collapse
Wow, I'm flattered. Also, thanks for the reg files!
GoodDayToDie said:
@clrokr: We gotta get you a RD tag, pronto! You're doing great things.
Click to expand...
Click to collapse
Seconded.
As far as MS's quote goes, I'm not 100% sure they will be setting out to patch it, but it's still a good idea to disable Windows Update anyways. They may be able to store some sort of cert blacklist in the UEFI that will block the executables required for this, even after a reinstall.
whats the difference between uefi,efi and firmware?
I find bootmgfw.efi,winload.efi in bcdedit.and I find surfacertuefi.bin in c:\windows\firmware.and every time I reinstall windows,there is a firmware in windows update.so is there anything flash into the surface hardware from window update?I think the uefi is just a file in the filesystem and its recovered when I reinstall windows from usb.
windowsrtc said:
whats the difference between uefi,efi and firmware?
I find bootmgfw.efi,winload.efi in bcdedit.and I find surfacertuefi.bin in c:\windows\firmware.and every time I reinstall windows,there is a firmware in windows update.so is there anything flash into the surface hardware from window update?I think the uefi is just a file in the filesystem and its recovered when I reinstall windows from usb.
Click to expand...
Click to collapse
No, the firmware (stored on-chip) is what you find in SurfaceRTUEFI.bin. The .EFI files are executables that can be loaded by this firmware if they are signed correctly.
Note: just because automatic updates are disabled doesn't mean you should ignore Windows Update. Quite the opposite, in fact, since this hack makes malicious exploits easier too. Just be very careful which patches you install.
clrokr said:
No, the firmware (stored on-chip) is what you find in SurfaceRTUEFI.bin. The .EFI files are executables that can be loaded by this firmware if they are signed correctly.
Click to expand...
Click to collapse
so uefi is checking efi ,but whats checking uefi?what will happen if we flash a modified uefi?
windowsrtc said:
so uefi is checking efi ,but whats checking uefi?what will happen if we flash a modified uefi?
Click to expand...
Click to collapse
The UEFI is currently the only thing capable of flashing a new UEFI, and it checks the signatures on any new UEFIs it flashes.
The only real way you could do it without relying on a signature check would be to open the tablet and solder onto the NAND directly.
Oh, there might be a JTAG port you could use... but yeah. Short of opening up the device (which the Surface, at least, is definitely not designed to support) there's not supposed to be any way to flash an unsigned firmware.
Also, the signature keys are probably stored in a TPM, so mucking with them isn't a practical option either if the EFI doesn't have a way to do it (which it doesn't).
GoodDayToDie said:
Oh, there might be a JTAG port you could use... but yeah. Short of opening up the device (which the Surface, at least, is definitely not designed to support) there's not supposed to be any way to flash an unsigned firmware.
Also, the signature keys are probably stored in a TPM, so mucking with them isn't a practical option either if the EFI doesn't have a way to do it (which it doesn't).
Click to expand...
Click to collapse
You can reset the TPM from Windows (change the owner password w/o knowing the previous one) and it doesn't break, I don't think they're stored in the TPM.
I have no idea what the TPM is used for.
GoodDayToDie said:
Also, the signature keys are probably stored in a TPM
Click to expand...
Click to collapse
No. There are lots of info on TPM, and it is not used to store CA keys.
A “Debug System” is will initially be identified by the presence of the Microsoft Test Signing CA in the UEFI signature database (“db”). The mechanism to identify debug machines may change, but the exclusion path logic should remain unchanged.
OEMs will need to work with their SOC supplier to provide the tools and process to implement “Debug Systems”.
To enable debug systems the db will need to contain the “Microsoft Testing Root Certificate Authority 2010”
....
Note: If there is a need to run unsigned tools, the system can be configured as a “Debug System” during manufacturing but there must be a step in the production process that removes the Microsoft Test CA. Production machines must not ship with the Microsoft Test CA in the db .
Click to expand...
Click to collapse
The last line explains the behavior I've seen on a just-bought VivoTab - I've seen lines about running unsigned files in CodeIntegrity eventlog. Seems that the device was provisioned with the unsigned tools, one of which deleted the certificate from uefi DB.
By the way, it should be theoretically possible to recover those tools on a just-bought device, if you would not go through the initial setup process but immediately press shift+f10 to run CMD and run a deleted-file recovery tool from there, or make a sector-by clone of disk C: to an SD card for later analysis. But, sadly, currently there are no such tools, and even if they are - they need to be signed by ms
Im using genuine Windows 8 Pro, and I dont see any benefits of this. But hey, I installed the "free" one on my friends computer. So this would be pretty handy for them, in case microsoft release an unfriendly patch
clrokr said:
So fire up regedit, go to
Code:
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\WindowsUpdate\Auto Update
and set the DWORD AUOptions to 0x00000000.
Only do this if you want to run unsigned apps!
[/QUOTE]
I navigated to this position in regedit and the key was already setted to 0x00000000
Might that be caused by the jailbreak tool published by netham45?
Click to expand...
Click to collapse
GoodDayToDie said:
Oh, there might be a JTAG port you could use
Click to expand...
Click to collapse
Even if you could find the JTAG it would be useless, Tegra processors lock out JTAG access when set to ODMPRODUCTION.
save_jeff said:
I navigated to this position in regedit and the key was already setted to 0x00000000
Might that be caused by the jailbreak tool published by netham45?
Click to expand...
Click to collapse
My tool does not set any settings of the sort.
netham45 said:
My tool does not set any settings of the sort.
Click to expand...
Click to collapse
Thx ;]
I would like to have this in the jailkreak tool as an optional funktion.
Maybe you could consider that :]
Just wondering why the registry hack is needed when you can simply disable the service? Seems like a more straightforward approach to me
bfosterjr said:
Just wondering why the registry hack is needed when you can simply disable the service? Seems like a more straightforward approach to me
Click to expand...
Click to collapse
Does not the service start again after restart of the system?
save_jeff said:
Does not the service start again after restart of the system?
Click to expand...
Click to collapse
You can permanently disable it.
Hi,
I started experimenting with this idea. I have WP8 files extracted from a firmware file. I copied these files to my surface RT. I was able to run some WP8 applications out of the box. however, applications that require UIXmobile.dll (WP GUI) failed to run. Now both WP8 and W8 share the NT core. so some libraries would just work. now the main WP8 library UIXmobile.dll doesn't work out of the box. as it uses a different function to create the gui for its applications.
I was thinking of something similar to what has been done by "mamaich", to implement a library that will replace the WP8 call wtith the standard W8 call (for example: use createProcess instead of createApplication) and pass the common calls to the already implemented APIs.
sadly , It's a very difficult task for me to do. I'll be spending time on it but i can't promise of any fast results.
I'd like to thank the authors of these threads for their wonderful work:
1. Running x86 apps on WinRT devices (by mamaich)
http://forum.xda-developers.com/showthread.php?t=2095934
2. RT Jailbreak Tool (By netham45 )
http://forum.xda-developers.com/showthread.php?t=2092158
3. Desktop apps ported to Windows RT (by GoodDayToDie)
http://forum.xda-developers.com/showthread.php?t=2092348
4. (FFU) ImgMount Tool v.1.0.15 (by AnDim)
http://forum.xda-developers.com/showthread.php?t=2066903
Which apps worked without tinkering?
Oh, very cool idea. It would probably only work for actual WP8 apps at first (not WP7.x apps, as those would require either a Silverlight or XNA runtime), but the idea has merit for sure. It was speculated for a long time that running WP8 apps on Win8/Windows RT would be possible, as both are written against the WinRT API, but that never happened. If we can make it happen ourselves, though... that would be awesome.
Of course, ideally we'd want to be able to access the store, since there aren't a lot of WP8 app packages floating around where we could use them. That's probably a very tricky problem in and of itself, although you could try extracting the store EXE and seeing what is required to make it work...
I think windows phone(os) is just a min gui shell for windows rt.so its possible to run the shell in windows rt.and maybe a windows phone can run windows rt.
windowsrtc said:
I think windows phone(os) is just a min gui shell for windows rt.
Click to expand...
Click to collapse
Not exactly. It's the same shell (well, the next rev) that was running on top of wince for WP7.
Is it an alternate shell (like Explorer), or a totally separate graphics subsystem?
Boomchaos said:
Which apps worked without tinkering?
Click to expand...
Click to collapse
there is a program called telwp.exe that was able to reach a certain point. I attached a screen shot of 3 different apps. 2 apps showed something before crashing (telwp, nokia_security). and the third app crashed with an error message. other wp apps usually crash silently leaving an error message about a faulty CoreUi.dll in the evenlog .
If I don't run the jailbreak, I cannot attach or create desktop process using WinDBG.
However under jailbreak everything works fine. I'd like to know why this happen.
Reserved
I believe they tried to prevent using the debugger on desktop apps for 8.1. Not sure how thorough it is; most of the time it's not really relevant as it's pretty easy to bypass.
GoodDayToDie said:
I believe they tried to prevent using the debugger on desktop apps for 8.1. Not sure how thorough it is; most of the time it's not really relevant as it's pretty easy to bypass.
Click to expand...
Click to collapse
I just updated to 8.1 to see how that works out with a old version of WinDBG. It doesn't work either. It seems being related to jailbreak. Curious how that will affect WinDBG.
Its a good question
A year or two back when we were first looking at RT 8.0, the fact that the debugger couldn't start or attached to desktop programs was a big headache
We were having to used the visual studio remote debugger
Then someone discovered that cdb -pv or -pvr would attach, and the opportunities opened up
Presumably normal attaching somehow falls foul of the locked down nature of the system
although strange it cant start existing signed exe's like notepad
or do a normal attach to them
so implies some other check is going on
In RT8.1 its even further tightened down
no admin level VS remote debugger
debugger package (and debug kit policy) cant even -pvr to a process
CORRECTION: yes you still can-pvr to a process
but cant access csrss as it is now protected
xsoliman3 said:
Its a good question
A year or two back when we were first looking at RT 8.0, the fact that the debugger couldn't start or attached to desktop programs was a big headache
We were having to used the visual studio remote debugger
Then someone discovered that cdb -pv or -pvr would attach, and the opportunities opened up
Presumably normal attaching somehow falls foul of the locked down nature of the system
although strange it cant start existing signed exe's like notepad
or do a normal attach to them
so implies some other check is going on
In RT8.1 its even further tightened down
no admin level VS remote debugger
debugger package (and debug kit policy) cant even -pvr to a process
CORRECTION: yes you still can-pvr to a process
but cant access csrss as it is now protected
Click to expand...
Click to collapse
You also can't write to the memory on a process if you attach to it.
For those of you missing Windows 8.1, congratulations, you just found the solution.
Download
OneDrive http://1drv.ms/1SGHo5e
MEGA https://mega.nz/#F!ks8gjaZT!oQx3xt9ET0nXe8JbKDvtsA
Features
1.Windows is fully updated as of February 2016.
2.Surface February update included (solves most speaker popping issue)
3.Based on Surface Pro 3 image. Full stock-like Surface branding (desktop background, out-of-box experience).
4.Windows activates with the embedded product key. Fully legit. I cannot guarantee if yours couldn’t activate though.
5.Bloat free with about 3 GB saving: (Microsoft devices are shipped bloat-free? Think again.) | Only 6 metro apps included (Camera, IE, OneDrive, PC Settings, Photos, Store). The rest can be downloaded from Store | Trial Office removed | Speech data removed.
6.Languages included: English, French, Spanish. Since it is Windows 8 Pro, you can download any other language later.
7.Fully working refresh and reset functionality.
8.WinRE from vanilla Windows, touchscreen driver included.
9.Pagefile takes less space: 400 MB. It can grow to up to 8 GB, a reboot brings it back to 400 MB.
10.Various Windows tweaks | File Indexing paused on battery | Verbose messages, you get more information in boots and shutdowns | No startup programs delay | non-certified DLNA devices are supported | Custom resolution script added (open C: drive, its there. Just double click.) | "Get Windows 10" system tray icon disabled.
11.Some drivers from S3, SP3, SP4, and other OEM devices (kudos to them for releasing their Skylake devices with Windows 8.1 drivers).
12.Latest Intel iGPU driver (version 4380 Beta).
NOT working
1.Windows Hello. As expected, Windows 8.1 does not support Windows Hello.
2.The buttons are mapped differently | Power --> Volume Down | Volume Up --> Power | Volume Down --> Start
3.Surface app | You cant adjust pen sensitivity | You can't configure the pen top button action through the app. You can still customize it manually with AHK.
FAQ
Q: Camera app crashes / BSOD
A: You need to disable the IR camera. You can do that either via the BIOS or Device Manager.
Q: The pen button doesn't work after the first setup
A: You may need to re-pair the pen. Go to PC Settings > Bluetooth and remove the Surface Pen. Create a new pairing by pressing the pen top button for 7 seconds, it will show up on the Surface, and just pair it.
Q: How did you get the embedded Windows 10 product key to work with Windows 8.1?
A: Actually I have no idea. It just worked.
Q: Are the "not working" issues going to be fixed?
A: For the buttons, its up to Microsoft to release a Windows 8.1 compatible driver, and we have no other source as Microsoft has modified Intel's driver. If you know how to remap the buttons (either via editing the driver, Registry, or AHK), please share it with us and I will include it in the next version. For the Surface app, I believe it is simply because the Windows 8 version of Surface app was not updated for the Surface Pro 4 (and will never be), so don’t expect that one.
Q: Why did you go with the beta driver for the graphics?
A: The latest release version, 4352 and 4364, are practically unusable. I experienced blank screen in video playback and some random BSOD. No choice really.
Q: When Intel has released the new driver, do I need to wait for the next version of the ROM?
A: No, you can just download and install it yourself without waiting for me to upload an updated ROM. The new version should pop up here, download the ZIP version for Windows 8.1, and install it using the "Have Disk…" method. Step-by-step guide http://www.windowscentral.com/how-install-intel-beta-graphics-drivers-surface
Q: How do I remap the pen buttons manually?
A: Go browse /r/Surface in Reddit, they have comprehensive guides on how to use AHK with the Surface Pen.
Q: Do I need to wait for your next ROM to get Windows updated?
A: No, you can just update normally via Windows Update
Q: You idiotic luddites should just upgrade to Windows 10 rather than shoehorning Windows 8 to the cutting-edge device that clearly does not deserve the old, ****ty Windows 8. Also, I am a Windows 10 fanboy.
A: Before you get angry and all that, I actually *do* want to upgrade to Windows 10. I mean, how cool is that to login with your face? However, it is hampered by quite a lot ergonomic usability issues, bugs, and the general quirkiness of Tablet Mode. As of today, Tablet Mode is nowhere near final. Not even the Task View has proper animation in Tablet Mode, it already tells how half-assed the Tablet Mode is.
How to install
BACKUP BACKUP BACKUP!!! This will format the entire disk. No data will be preserved! Its also advised to remove the microSD card during the process.
0. Get a keyboard and USB hub if you don’t have the Type Cover.
1. Download and extract the package
2. Set up the ISO image on a CD or USB stick. If you use Rufus, set it on "MBR for UEFI computer" (only for the USB stick, the Surface will be set up as GPT)
3. Boot it on the Surface
4. Enter cd /d D:\scripts
5. Enter diskpart /s part.txt
6. Enter apply D:\Images\install.wim D:\Images\winre.wim
7. You can repeat the step #6 just to be sure
8. Reboot, unplug the USB stick.
Signed up on xda just to express my gratitude for this great tutorial and release. Everything worked a charm with full touchscreen support and I am so glad to finally have Windows 8.1 on my Surface Pro 4! No more forced windows updates sucking up my bandwidth, more free space on my hard disk, and the only gaming app that I use for my ps2 games (PCSX2), finally runs at 60fps (can you imagine on windows 10 the emulator would drop between 40-50 fps)!!! Thanks again for making my day!
ptrkhh, did you by any chance figure out how to configure the power and volume buttons???
For now I'm using volume up button to turn the tablet on and off and the power button to turn the volume down.
Fan-damn-tastic!!!
Like the other person above, I made an account just to express my EXTREME gratitude for the amazing work that was done.
I just got myself a surface book for dirt cheap, fantastic device, horrible OS. I'm not one to shy away from randomly screwing with things, so on my research for windows 8 installs for the Book, I found this absolute GEM of a post.
Downloaded the image, and threw it on my Surface Book and here's what happened:
a) installed flawlessly
b) activated instantly
c) everything that works on the Pro, works on the book. The keyboard and mouse work too!!!
d) The BIG one... the DETACH...... IT WORKS!!! Hold the detach button like normal, and, granted it seems to take a second or so longer than it did on Win10, but it releases JUST fine.
e) the dual batteries. I didn't test it for long, but Win8 seems to drain the base battery and leave the tablet battery alone.
f) the power /vol buttons do the same thing as the pro4, but i really don't care. Actually, the Book doesn't have a windows button on the tablet, so the vol down button doing that is actually a HUGE plus for me. Screw the volume controls!
g) i have not figured out the nvidia drivers yet, but i also haven't tried too hard yet. So that's a negative so far.
h) Front camera does weird infared things. It will be disabled.
I would imagine even if i get the dual gpu to work, if i start a program with the nvidia, and disconnect the screen, it will probably go all fubar and need a hard restart. The latch seems to run independently from the rest, and without software watching it, it WILL do what you tell it to, period. (my assumption, haven't tried it yet)
Battery life has not been tested much yet.
Device manager shows 2 unknown devices. I'm assuming one is the GFX card, the other one, probably the detatch button. If that's not it i have no idea. Really don't care though.
Updates pick up on new driver versions just fine. (again, so far)
I have the i5 version w/dual gfx. I have no idea what will and won't happen with the i7, the i7 with nvidia, or the newest performance base with the better nvidia gfx. I doubt much will be different, but much as I did, proceed at your own risk!
I hope this was useful, and if it was, let everyone know it works!!!!
If anyone wants, I can post an update after I finish setting it up, and had some real-life usage of it. If not, my feelings will not be hurt!
Awesome!
Works almost perfect on my Surface Pro 4.
But somehow it cannot auto rotate and the touch keyboard is not popping up (even in metro apps).
Does anybody know how to fix that?
Edit: you have to reboot and remove the keyboard before windows boots to get it working.
The OneDrive link is dead, can you get a new link? Mega isn't working for me
Would this work on a surface 3?
Surface pro 4 BSOD
Hi, I have the i5 version surface pro 4 and when i use the image above or a fresh copy of windows 8.1 pro it finishes installing then blue screens with internal power error. Any ideas as to get past this.
Cheers
I have the same problem.
When it finishes installing, I get a blue screen saying there is a problem with the BCD. I tried booting with a Windows 10 ISO to use the startup repair tool to fix it, but it says it can't. I've tried it 3 or 4 times; it did work once, but I wanted to try a different Windows, so I wiped it. Now I can't get it to work again. I did all the diskpart stuff, and the apply, all seemed to work until final boot = bsod. The apply.cmd is supposed to do the configuring, I think. Anybody else had this problem?
Surface Pro 4 factory restore
Hi" have you tried going to the Microsoft site and downloading the factory image. Just take the ISO and make into USB bootable. It will install everything and recreate all partions. Hope this helps.
Does anyone know If this will work on Surface pro 6????
I ran into an issue with my Surface pro 6 that gives me the BSOD every time I connect my type cover!!! I tried everything! I ran all the diagnostics and went through almost every safe steps and was able to fix the corrupted files. I even did all the driver diagnostics!!! It is very frustrating because I even did a factory reset and I'm still having the same issue... I'm hoping to be able to safely downgrade to Windows 8.1 to see if it fixes the issue, then upgrading to Windows 10 again. That's the last thing I can think of.
Does it work on SP4 2017???
I have the same problem.
When I tried to install this ROM on my Surface pro 4 2017, it gives me the BSOD.
Commands do not work, it says right no the first: "The system cannot find the path specified"
i also have the same problem on my surface pro 6
How to install a version of 8.1 on SP4-SP6
If you get that INTERNAL_POWER_ERROR, you most likely have a Kaby Lake processer which only supports Windows 10. The only version of 8.1 that works on a Kaby Lake Surface Pro 4+ is Windows Server 2012 R2.
asking for drivers
ptrkhh said:
For those of you missing Windows 8.1, congratulations, you just found the solution.
Features
1.Windows is fully updated as of February 2016.
2.Surface February update included (solves most speaker popping issue)
3.Based on Surface Pro 3 image. Full stock-like Surface branding (desktop background, out-of-box experience).
4.Windows activates with the embedded product key. Fully legit. I cannot guarantee if yours couldn’t activate though.
5.Bloat free with about 3 GB saving: (Microsoft devices are shipped bloat-free? Think again.) | Only 6 metro apps included (Camera, IE, OneDrive, PC Settings, Photos, Store). The rest can be downloaded from Store | Trial Office removed | Speech data removed.
6.Languages included: English, French, Spanish. Since it is Windows 8 Pro, you can download any other language later.
7.Fully working refresh and reset functionality.
8.WinRE from vanilla Windows, touchscreen driver included.
9.Pagefile takes less space: 400 MB. It can grow to up to 8 GB, a reboot brings it back to 400 MB.
10.Various Windows tweaks | File Indexing paused on battery | Verbose messages, you get more information in boots and shutdowns | No startup programs delay | non-certified DLNA devices are supported | Custom resolution script added (open C: drive, its there. Just double click.) | "Get Windows 10" system tray icon disabled.
11.Some drivers from S3, SP3, SP4, and other OEM devices (kudos to them for releasing their Skylake devices with Windows 8.1 drivers).
12.Latest Intel iGPU driver (version 4380 Beta).
NOT working
1.Windows Hello. As expected, Windows 8.1 does not support Windows Hello.
2.The buttons are mapped differently | Power --> Volume Down | Volume Up --> Power | Volume Down --> Start
3.Surface app | You cant adjust pen sensitivity | You can't configure the pen top button action through the app. You can still customize it manually with AHK.
FAQ
Q: Camera app crashes / BSOD
A: You need to disable the IR camera. You can do that either via the BIOS or Device Manager.
Q: The pen button doesn't work after the first setup
A: You may need to re-pair the pen. Go to PC Settings > Bluetooth and remove the Surface Pen. Create a new pairing by pressing the pen top button for 7 seconds, it will show up on the Surface, and just pair it.
Q: How did you get the embedded Windows 10 product key to work with Windows 8.1?
A: Actually I have no idea. It just worked.
Q: Are the "not working" issues going to be fixed?
A: For the buttons, its up to Microsoft to release a Windows 8.1 compatible driver, and we have no other source as Microsoft has modified Intel's driver. If you know how to remap the buttons (either via editing the driver, Registry, or AHK), please share it with us and I will include it in the next version. For the Surface app, I believe it is simply because the Windows 8 version of Surface app was not updated for the Surface Pro 4 (and will never be), so don’t expect that one.
Q: Why did you go with the beta driver for the graphics?
A: The latest release version, 4352 and 4364, are practically unusable. I experienced blank screen in video playback and some random BSOD. No choice really.
Q: When Intel has released the new driver, do I need to wait for the next version of the ROM?
A: No, you can just download and install it yourself without waiting for me to upload an updated ROM. The new version should pop up here, download the ZIP version for Windows 8.1, and install it using the "Have Disk…" method. Step-by-step guide
Q: How do I remap the pen buttons manually?
A: Go browse /r/Surface in Reddit, they have comprehensive guides on how to use AHK with the Surface Pen.
Q: Do I need to wait for your next ROM to get Windows updated?
A: No, you can just update normally via Windows Update
Q: You idiotic luddites should just upgrade to Windows 10 rather than shoehorning Windows 8 to the cutting-edge device that clearly does not deserve the old, ****ty Windows 8. Also, I am a Windows 10 fanboy.
A: Before you get angry and all that, I actually *do* want to upgrade to Windows 10. I mean, how cool is that to login with your face? However, it is hampered by quite a lot ergonomic usability issues, bugs, and the general quirkiness of Tablet Mode. As of today, Tablet Mode is nowhere near final. Not even the Task View has proper animation in Tablet Mode, it already tells how half-assed the Tablet Mode is.
How to install
BACKUP BACKUP BACKUP!!! This will format the entire disk. No data will be preserved! Its also advised to remove the microSD card during the process.
0. Get a keyboard and USB hub if you don’t have the Type Cover.
1. Download and extract the package
2. Set up the ISO image on a CD or USB stick. If you use Rufus, set it on "MBR for UEFI computer" (only for the USB stick, the Surface will be set up as GPT)
3. Boot it on the Surface
4. Enter cd /d D:\scripts
5. Enter diskpart /s part.txt
6. Enter apply D:\Images\install.wim D:\Images\winre.wim
7. You can repeat the step #6 just to be sure
8. Reboot, unplug the USB stick.
Click to expand...
Click to collapse
Dear ptrkhh,
Thank you very much. Without your excellent work, people can still not use SP4 installing Windows 8.1 or even Server 2012(based on Windows 8.1 framwork and also working with Windows 8.1drivers). Because there are many versions of both Windows 8.1 or even Server 2012, I was tring to collect the drivers that SP4 can work.It is hard to find touchscreen driver from vanilla Windows, and there so many drivers to test from S3,SP3,OEM. Could you please share the Surface Pro 4 drivers for Windows 8.1 separately, or give us a guide to lead to download each drivers. Hope you have a nice day
repo006 said:
Dear ptrkhh,
Thank you very much. Without your excellent work, people can still not use SP4 installing Windows 8.1 or even Server 2012(based on Windows 8.1 framwork and also working with Windows 8.1drivers). Because there are many versions of both Windows 8.1 or even Server 2012, I was tring to collect the drivers that SP4 can work.It is hard to find touchscreen driver from vanilla Windows, and there so many drivers to test from S3,SP3,OEM. Could you please share the Surface Pro 4 drivers for Windows 8.1 separately, or give us a guide to lead to download each drivers. Hope you have a nice day
Click to expand...
Click to collapse
Hi, thank you, it means a lot to me. Unfortunately I no longer have the device nor copies of the driver. Quite surprisingly many drivers are actually available online, you may want to consider using the software called "Snappy Driver Installer" (SDI), it is able to find drivers suitable for your device. The ones I formulated myself are under the folder "bastard drivers.rar", which is not many if I remember correctly.
For the touchscreen functionality in particular, it needs the graphics driver. Once you have the graphics driver installed, touchscreen should work instantly.
How much free ram is there after a fresh install?
I have ram shortage issues in Win10 with my 4GB Pro4. I'm not a fan of Win10 either but I sure wish I could just disable crap and free up the ram instead of downgrading.
Does the front webcam and mic work ok? I use mine frequently. Thanks!