It is all resulting from the technique, how DISM works. DISM basically (after image is mounted) 1st-ly only PROPOSE changes after commands like "DISM /image:C:\mount /Add-Package /PackagePath:C:\MSU" (adding MSUs) a then saves them with unmount "Dism /unmount-WIM /MountDir:C:\mount /Commit" or discards them with unmount "Dism /unmount-WIM /MountDir:C:\mount /Discard"... Some changes CAN'T be proposed together (because they address one issue deep in the OS), so then only 1st colliding change can be proposed (kb2919442, kb2975061, kb2939087), then changes has to be commited to WIM file by "Dism /Commit-Image /MountDir:C:\mount", then 2nd colliding change can be proposed (kb2919355 with rest of the MSUs)... ...so the procedure HAS TO be like mentioned...
Ok, I will try one last time, your way and see if it works. Thanks. BTW, on your first post you say 135 pieces, there is 145 .msu files in that list, (146 total if you include the hotfix)..at least that's what my notepad++ tells me...
Yep, 146, It was my typo, because I have stored "Update 1" (11 MSUs separatelly - HotFix included)...
moderate your a genius! It worked this time! Whoohoo only about 30 updates where needed (office 2013 updates, system hardware update,KB2894856, and defender definitions), and one reboot this time!...soo much better then over 70 and having to restart like 5 times and wait hours. I am going to upload it to my OneDrive for safe keeping. I edited this post with the link after in case someone else would like it. Thanks for your help! Edit: Download Links: WinRT_8_1_Surface_2_Oct2014.zip > 1drv.ms/1w35QQC Surface-2-Drivers-Oct-2014.zip > 1drv.ms/1w34UvB Batch files I used; for install.wim Code: Dism /Mount-Wim /WimFile:C:\Integrate\WIM\install.wim /Index:1 /MountDir:C:\Integrate\MOUNT Dism /Image:C:\Integrate\MOUNT /Add-Driver /Driver:C:\Integrate\DRIVERS /Recurse Dism /image:C:\Integrate\MOUNT /add-package /packagepath:C:\Integrate\UPDATE1\ Dism /Commit-Image /MountDir:C:\Integrate\MOUNT Dism /image:C:\Integrate\MOUNT /add-package /packagepath:C:\Integrate\UPDATES\ Dism /Unmount-Wim /MountDir:C:\Integrate\MOUNT /Commit Pause UPDATE1 Had kb2919442, kb2975061, kb2939087 UPDATES had the rest For boot.wim Code: Dism /Mount-Wim /WimFile:C:\Integrate\WIM\boot.wim /Index:2 /MountDir:C:\Integrate\MOUNT Dism /Image:C:\Integrate\MOUNT /Add-Driver /Driver:C:\Integrate\DRIVERS /Recurse Dism /Unmount-Wim /MountDir:C:\Integrate\MOUNT /Commit Pause
When two changes collide and image is ruined, then 2nd colliding change is partially integrated. So you can calmly have OneDrive and Search button on start page on ruined image, still the updates are re-offered.
Hi Moderate, I have a Nokia 2520 which wont boot I received a recovery ley from microsoft is this the as the productos ley? If so how do I reinstall the windows rt to it? Thanks
No, recovery key let you bypass "Bitlocker device encryption", which is needed to erase whole partition in reinstallation process. "Bitlocker device encryption" is special version of Bitlocker used in Windows RT. When you turn on the device, how far you can get? Where are you from (country)? Do you have Instant Messenger (Skype, ICQ, MSN, GTalk...)? Send me PM.
1. These commands executed under elevated CMD.EXE will give Safe Mode option at startup. But you need to plug the keyboard to USB slot to access Safe Mode (enter password). Code: bcdedit /set {default} safeboot minimal bcdedit /copy {default} /d "Windows RT 8.1 Safe Mode" bcdedit /deletevalue {default} safeboot bcdedit /timeout 3 2. Since it is impossible to disable Lock screen by GPEDIT.MSC in Windows RT, here is special REG file to achieve the goal: Code: Windows Registry Editor Version 5.00 [HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Microsoft\Windows\Personalization] "NoLockScreen"=dword:00000001 BTW: I still don't understand the lock screen purpose.
It only boot to a blue screen with sad face. And has a file error. I have a US AT&T version. Yes I have Skype. Can't send PM yet need to post more.
Here is recommendation: 1. After your device starts booting press and hold both <Windows> key and <Power> key to turn it off BEFORE the BlueScreen appears (You have to be quite quick to make that, basically you should press and hold both buttons immediately after you press power button to turn the device on, but power button has to be pressed two times - one time for turn on and second time together with Windows button and finger holding.). 2. You need to do it three times in total and then start fourth boot. 3. At fourth boot (after three previous booting fail by your forced powerdowns) Automatic Recovery process will start from Recovery partition. 4. Select "TroubleShooting" and then "Reset to factory settings" in the blue touch menu. 5. When prompted insert the recovery key, what had you received. 6. System will reinstall and it should work.
I already tried this and gave an error in the process. Will retry again when I get home and will post the result. Thanks
There is another option: Try to boot from USB flash, where you can put the customized boot.wim and install.wim image. You can make bootable flash disk in W8-1 x64 or x32 to create 32GB FAT 32 partition with valid boot record (by running RecoveryDrive.exe), then you can delete (not format) all files there (since they arn't arm) and I can send you bootable Nokia 2520 image, which you will copy there. Then however, you need to reach bootmenu (from recovery partition again by three power interrupts) and select there "Use Device" and "USB Class Device".
Bad luck, can't reach the boot menu. I was able to get it but right now is not working. What can I do? Is there a way to obtain the product key from AT&T? So I can reinstall everything again. Moderate what do you recommend??
[Quote = wpagan79; 962231] La mala suerte, no se puede acceder al menú de arranque. Tuve la oportunidad de conseguirlo, pero en este momento no está funcionando. ¿Qué puedo hacer yo? ¿Hay una manera de obtener la clave de producto de AT & T? Así que puedo volver a instalar todo de nuevo. Moderado ¿qué recomienda ?? [/ quote] When boot it says Preparing Automatic Repair, then the following error shows Tour PC ran into a problem and needs to restart. We're justo collecting some error info, and then we'll restart forma you. Then it shows some error name which changes with each try. Help me out I love My table, don't want to losse it.
Nice, but those are LP for W8-1 x32 (NOT for ARM). LP for ARM always consists from two files (CAB for WRT and EXE for ORT)...
I am multilingual DVD, how to integrate its language to the install.wim ? With the cab and exe Thanks for your help
Grab (French) language CAB from: MICROSOFT.WINDOWS.RT.8.1.LANGUAGE.PACK-CL1_CL2.AND.LP.RTM.WOA.DVD-WZT.nfo Then integrate it into install.wim. (Like this...) Code: DISM /Mount-Wim /WimFile:C:\ISO\sources\install.wim /index:1 /MountDir:C:\mount dism /image:C:\mount /Add-Package:"C:\CAB\Microsoft-Windows-Client-LanguagePack-Package~31bf3856ad364e35~arm~cs-CZ~6.3.9600.16384.cab" Dism /unmount-WIM /MountDir:C:\mount /Commit
RT Speciality - Modular HAL: Here is something very special... on ARM systems your HAL layer is divided to: 1) Base HAL - found in NTOSKRNL.EXE and HAL.DLL (just like on x32 and x64) 2) HAL Extensions - DLLs (HAL Devices in Device Manager) customized by HW vendor. HAL extensions are made for specific Windows RT version (8-1-x vs 8-0-0), so you can't downgrade freely WITHOUT finding suitable HAL extension (NOT necessarily from your HW vendor, since some HW configurations are similar), but certainly for right RT version. Otherwise you risk HAL initialization failed error aka 0x0000005c. For that purpose, maybe you will find nice the opportunity to dig in the other vendors drivers. )