[Download:] Windows 10 RS3 RTM b16299.15 PE arm32

Discussion in 'Windows 10' started by moderate, Oct 12, 2017.

Tags:
  1. moderate

    moderate MDL Guru

    Aug 31, 2009
    2,648
    2,153
    90
  2. samuel.caldas

    samuel.caldas MDL Novice

    Dec 18, 2017
    1
    0
    0
    you used lumia drivers on surface rt?
     
  3. moderate

    moderate MDL Guru

    Aug 31, 2009
    2,648
    2,153
    90
    I used Lumia drivers on Lumia 2520 device. For Surface 1 or 2 (RT) you will need drivers for Surface 1 or 2.
     
  4. NokiaLumia2520

    NokiaLumia2520 MDL Novice

    Jan 1, 2018
    1
    0
    0
    Have you installed it on your 2520? How does it run? Is it worth going for it or better to stay with 8.1?
    Also how do I know if my secure boot on 2520 is unlocked?
     
  5. DeputyHuber

    DeputyHuber MDL Novice

    May 14, 2018
    1
    0
    0
    Any suggestions on where I can find the Surface 1&2 drivers? Seems like a good way to breathe new life into a dated device.
     
  6. Jaydon Graham

    Jaydon Graham MDL Novice

    May 16, 2018
    2
    0
    0
    I just read something about being able to copy the old drivers from the 8/8.1 install from C:\Windows\System32\DriverStore\FileRepository. This is the path for a normal x86/64 install anyway.
     
  7. Jaydon Graham

    Jaydon Graham MDL Novice

    May 16, 2018
    2
    0
    0
    were you able to replace the installed windows 8.1 rt on your tablet with this? im working on driver injection and tinkering with this for the surface rt and surface2 rt
     
  8. moderate

    moderate MDL Guru

    Aug 31, 2009
    2,648
    2,153
    90
    Drivers? Easy thing, after the mounting of your original WRT 8-1 WIM (boot.wim, install.wim, winre.wim) just:

    List Drivers:
    dism /image:C:\mount /get-drivers /all /format:table > C:\DriverLog.txt

    Extract Drivers:
    dism /image:C:\mount /export-driver /destination:C:\Drivers

    WinPE 10 arm32 works on Surface 1 and 2. On Lumia 2520 it doesn't work.
     
  9. Rhunt56

    Rhunt56 MDL Novice

    Jul 10, 2018
    3
    0
    0
    I have a Surface 2 RT with 8.1 OS. How do I unlock the Secure Boot?
     
  10. moderate

    moderate MDL Guru

    Aug 31, 2009
    2,648
    2,153
    90
    1. Flash unlocked policy by downloading and running "Longhorn's Package"
    2. Uninstall KB updates, which "fixes" the unlock
    3. Set TestSigning ON in BCD by BCDEdit.exe for sections: {Current} and {BootMgr}
     
  11. Rhunt56

    Rhunt56 MDL Novice

    Jul 10, 2018
    3
    0
    0
    I found a Longhorn Packet 1.21 iso file. Is this what your referred to?
     
  12. Rhunt56

    Rhunt56 MDL Novice

    Jul 10, 2018
    3
    0
    0
    Thank you.
     
  13. itsmemario1

    itsmemario1 MDL Senior Member

    Sep 10, 2012
    275
    24
    10
    #15 itsmemario1, Jul 18, 2018
    Last edited: Jul 18, 2018
    omg wait what ? :'D

    I have a Surface 2 thats running Update 3 of Windows RT 8.1 with all recent updates here.
    (64gb version)

    So, to get this 100% straight I do as follows :

    1. Flash the Policy
    Run InstallPolicy.cmd as admin.

    2. Uninstall all of the evil kb's from the screenshot

    3. reboot

    4. cmd as admin

    bcdedit /set {default} testsigning on && bcdedit /set {bootmgr} testsigning on

    5. I rescue all drivers from C:\Windows\System32\DriverStore\FileRepository.

    6. Install Windows 10 PE arm32...from USB Stick...as update ?
    Maybe there is an ISO around ?

    7.

    I can then use all 32 bit x86 applications, like FIrefox or VLC, because thanks to an built in "emulator" ? :O

    Is everything correct ?
     
  14. moderate

    moderate MDL Guru

    Aug 31, 2009
    2,648
    2,153
    90
    #16 moderate, Jul 19, 2018
    Last edited: Jul 19, 2018
    (OP)
    Steps: 1. - 4. are quite correct for getting into the RT 8.1 Test Mode (but auto-reboot will also occur after step 1)

    But you will also need to:
    X. disable WU auto-updating by importing this REG:
    Code:
    Windows Registry Editor Version 5.00
    
    [HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\WindowsUpdate\Auto Update]
    "AUOptions"=dword:00000001
    "CachedAUOptions"=dword:00000001
    "ElevateNonAdmins"=dword:00000001
    "ForcedReboot"=dword:00000002
    "IncludeRecommendedUpdates"=dword:00000001
    
    For making Win10PE USB flash boot drive:
    5. Extract Drivers from running Windows 8.1 RT:
    dism /online /export-driver /destination:C:\Drivers

    6. Integrate Drivers to WinPE:
    DISM /Mount-Wim /WimFile:C:\winpe.wim /index:1 /MountDir:C:\WinPE
    Dism /Image:C:\WinPE /Add-Driver /Driver:C:\Drivers /Recurse
    Dism /unmount-WIM /MountDir:C:\WinPE /Commit

    7. Extract WinPE on USB Flash drive formatted to FAT32:
    dism /apply-image /imagefile:C:\winpe.wim /index:1 /applydir:[Flash-Drive-Letter]:\

    8. Create new boot-BCD on USB drive formatted to FAT32:
    bcdboot [Flash-Drive-Letter]:\Windows /s [Flash-Drive-Letter]: /f UEFI

    or alternativelly:
    8. Create new boot-BCD on USB drive formatted to FAT32:
    bcdboot C:\Windows /s [Flash-Drive-Letter]: /f UEFI

    9. Edit new BCD:
    bcdedit /store [Flash-Drive-Letter]:\EFI\Microsoft\Boot\BCD /set {bootmgr} testsigning on
    bcdedit /store [Flash-Drive-Letter]:\EFI\Microsoft\Boot\BCD /set {default} testsigning on
    _______________________________________________________________
    After 1.-4.+X. you will be able to run ALSO :
    a) win32 (=non-Metro) arm32 programs from 3rd parties
    b) and .NET v4.x (=non-Metro) AnyCPU programs from 3rd parties
    ...if they will be signed with any signing certificate. (There also exist certificates for other purposes like crypting etc., it has to be certificate created for signing purpose.)

    After 5.-9. you will get no new run options other than those mentioned in "After 1.-4.+X." section.
    There is no x32 Emulator in Win10PE arm32.
    There is no x32 Emulator even in any WinPE arm32.
    There is no x32 Emulator even in full Windows 10 arm32 (unpublic).
     
  15. itsmemario1

    itsmemario1 MDL Senior Member

    Sep 10, 2012
    275
    24
    10
    Thanks a lot for these detailed informations ! :'D
    Much appreciated !

    a.) I created the Win10PE USB Stick exactly as you explained ! CHECK
    Thanks a million times for this ! :D

    b.) Started my Surface 2 RT and ran "InstallPolicy.cmd" as admin. CHECK

    c.) On Restart it asked to accept the Secure Boot Policy (I clicked accept) CHECK
    (it booted into Windows just fine then)

    d.) I uninstalled all infected kbs from your screenshot CHECK
    There only was 1 of these installed anyway (KB4284815), even if I had "Update 3" and all recent updates installed (until today) @_@ (?)


    deinstalled kbs.jpg

    I did not uninstall the Myrias Jailbreak KBs, as I was using longhorn Jailbreak.

    e.) I imported the REG file you listed, into the now cleaned up Windows 8.1 RT CHECK


    f.) I restarted the Surface 2 RT (It said is installing Updates, couldnt really read, as it was too fast)
    But it kept reinstalling updates after the restart to 100%...I guess :

    f_1.) It was just the final deinstallation of the KB

    f_2.) I guess I should have deleted the Software Distribution Folder 1st, so that no more (old) updates are on the Surface, that could be installed after a restart.


    g.) I then wanted to open CMD as admin within Windows 8.1 RT to set the tablet into test mode
    bcdedit /set {default} testsigning on && bcdedit /set {bootmgr} testsigning on

    Windows then said "the value is protected by the guideline for secure boot"...guess I have to run the"InstallPolicy.cmd" once again ?
    And then reboot to try CMD as admin again ? Or am I mixing something up here ?

    I WENT TO BED xD

    g.) I will then restart the Surface 2 RT
    and boot from the USB Stick to install Windows 10 PE, by Starting the Suface 2 by holding down VOLUME DOWN + POWER BUTTON
     
  16. moderate

    moderate MDL Guru

    Aug 31, 2009
    2,648
    2,153
    90
    #18 moderate, Jul 20, 2018
    Last edited: Jul 20, 2018
    (OP)
    When you unistalled KB4284815, then Windows [in step f.)] will auto-install from WinSxS another older infected one KB (what was previously superseded/replaced by KB4284815).
    So after the reboot, you need to check list AGAIN and if you find another infected KB and restart, then you need to do another check AGAIN until you will find no another update to remove. So you can calmly end up checking the list 16x or so. But you can look into the history to display only newly installed updates, so it is still easy.

    "the value is protected by the guideline for secure boot" means, that some infected update is still installed.
     
  17. itsmemario1

    itsmemario1 MDL Senior Member

    Sep 10, 2012
    275
    24
    10
    #19 itsmemario1, Jul 21, 2018
    Last edited: Jul 21, 2018
    Thanks for the advice !

    That is quite "interesting". :)
    It does indeed keep installing previous infected kbs, after each restart/deinstallation of a kb.

    I had to restart 2 times (kb4103725) and (kb4074594). All infected kbs are gone now.

    The policy seems to stay installed, but I could still not use CMD (admin) with the :
    bcdedit /set {default} testsigning on && bcdedit /set {bootmgr} testsigning on
    it still says protected.

    So I ran the policy thing once more, accepted installation on a reboot and went for "bcedit" again...still protected.

    deinstalled kbs part 2.jpg

    Desperately I went for the kbs below the longhorn patch...

    deinstalled kbs part 3.jpg

    October patches werent even there and I stopped at the "normal" Updates...still, "bcedit" says protected.
    (Normal Update only had kb3128650 anyway...which I uninstalled)

    I even clicked the REG file again, but it said already exisiting.

    I then remembered I can enter the UEFI "menu/bios" by holding volume UP + pressing Power Button.
    But I cant enter the uefi/bios anymore...keyboard will only light up and fade to black ? :S
    (ah damn that was another tablet...this is ARM...still funny its stuck at keyboard lights only when using vol up+power)

    Maybe this has to do something with Update 3 I installed (aka. enable Windows 10 look) ? Shall I install the "recovery" image and try from scratch ?
     
  18. moderate

    moderate MDL Guru

    Aug 31, 2009
    2,648
    2,153
    90