paraglider
-
Posts
12 -
Joined
-
Last visited
paraglider's Achievements
-
If you can't mount win 10 images with dism or imagex then I don't think the WTK author can help you. Its likely that your windows 8.1 is messed up in some way. I just tried on the same windows 8.1 as before and I have no problem mounting the windows 10 install.wim with the windows 8.1 dism.
-
Just to prove it works: http://paraglidernc.com/Files/dism.png
-
I installed the windows 10 adk and started the deployment tools command line. dism runs ok and reports its version 10.0.10240.16384. If I explicitly run from "c:\Program Files (x86)\Windows Kits\10\Assessment and Deployment Kit\Deployment Tools\amd64\DISM\dism.exe" it also works. I am running windows 8.1 x64 enterprise edition.
-
And I have just tried win 10 dism on win 8.1 x64 to mount a windows 10 install.wim. It works without problem.
-
I tried win 10 imagex on win 8 and win 8.1. It runs without problem.
-
Thats why the win 10 dism folder has all these files: api-ms-win-core-apiquery-l1-1-0.dll api-ms-win-downlevel-advapi32-l1-1-0.dll api-ms-win-downlevel-advapi32-l1-1-1.dll api-ms-win-downlevel-advapi32-l2-1-0.dll api-ms-win-downlevel-advapi32-l2-1-1.dll api-ms-win-downlevel-advapi32-l3-1-0.dll api-ms-win-downlevel-advapi32-l4-1-0.dll api-ms-win-downlevel-kernel32-l1-1-0.dll api-ms-win-downlevel-kernel32-l2-1-0.dll api-ms-win-downlevel-ole32-l1-1-0.dll api-ms-win-downlevel-ole32-l1-1-1.dll api-ms-win-downlevel-shlwapi-l1-1-0.dll api-ms-win-downlevel-shlwapi-l1-1-1.dll api-ms-win-downlevel-user32-l1-1-0.dll api-ms-win-downlevel-user32-l1-1-1.dll api-ms-win-downlevel-version-l1-1-0.dll compatprovider.dll dism.exe dism.psd1 dism.psm1 dism.Format.ps1xml dism.Types.ps1xml dismapi.dll dismcore.dll dismcoreps.dll dismprov.dll ext-ms-win-advapi32-encryptedfile-l1-1-0.dll ffuprovider.dll folderprovider.dll imagex.exe imagingprovider.dll logprovider.dll Microsoft.Dism.Powershell.dll pkgmgr.exe ssshim.dll vhdprovider.dll wimgapi.dll wimmount.sys WimMountInstall.exe wimprovider.dll wimserv.exe wofadk.sys
-
Not true. However windows 10 adk utilities have dependencies on other dlls that you also have to copy or add to a folder in the path.
-
Note unfortunately wtk makes it difficult to replace the version of imagex it uses ( it has configuration options to specify the version of dism it uses though ). I just copy the latest version to C:\Windows\WinToolkit_Temp\Files after it copies the file there.
-
If you want to download adk components without downloading the huge adk then search for getwaiktools. Or download full ADK from MS at: http://go.microsoft.com/fwlink/p/?LinkId=526740
-
Start an elevated command line. Run: imagex /cleanup Reboot. Start an elevated command line run: mkdir C:\WinToolkit_Mount "C:\Windows\WinToolkit_Temp\Files\Imagex.exe" /mountrw "C:\Users\Administrador\Desktop\Win10ISO\SOURCES\install.wim" 1 "C:\WinToolkit_Mount" If that fails then you may have more information. If it works then run: imagex /unmount C:\WinToolkit_Mount It is generally recommended that you copy the source to the folder in the root of a drive like c:\win10iso I have no problem integrating win10 updates on win10 so it may be a backlevel problem. You will more than likely need win10 dism / imagex which you can get from w10 adk.
-
Same for me. I installed 8.1 and 10 onto a gpt formatted intel 750 nvme ssd with a rufus formatted USB stick. All window installs are on the ntfs partition. RUFUS creates a small fat32 partition with a uefi ntfs driver that enables booting from the ntfs drive.
-
Not true. My system is 8.1 X64. I had no problems upgrading win10 10049 pro image to enterprise image using 10049 dism. Worked with both x86 and x64 windows 10049. Verified that both upgraded enterprise images installed ok and used enterprise key for activation.