Just a question, Bordi - what browser are you using?
No screenshots!
The ISO folder location is irrelevant as long as it is consistent during the process. I had to change it from C: to J: when I posted earlier. If DISM loaded the WIM from an ISO on the D: drive, It expects the wim file to go back to the same place.
I use Firefox and internet explorer but 99% of the time I use Firefox now
Just that chrome allows you to press prnt scr like this and then ctrl+vand the screen is captured and posted to this reply box - just saying.
OK mate thanks I’ll give it a go tomorrow, see how I get on
I have come across a few reports of DISM failing to handle wim mounts as it should, it seems sometimes to be a 64-bit Windows phenomenon. There are 2 DISM.Exe programs from Windows\System32 and from Windows\SysWOW64 in 64-bit Windows system. It appears that the "wrong" version cannot pick up after the right version has started a process, but the single copy 32-bit version has problems too. :
Hi all,
had same problem unmounting the wim file using Windows 7 Pro 32bit.
My solution was: Checking for "wrong" Dism.exe
Preparing a WinPE I followed the steps in the help of AIK. I ran the
copype.cmd batch. When it was finished, it said that it added something
to the path environment variable. It was clear that it did so in order
to find the tools needed for the further steps. As long as everything
worked, I didn't give it a second thought. Then I could not unmount the
WIM.
I looked at the PATH variable: NO entry pointed to the directory where
dism.exe was in. (In my case that would have been
c:\program files\windows aik\tools\x86\servicing
)
Magically, dism.exe started from everywhere though.
Doing a dir c:\dism.exe /s /a showed I had a Dism.exe in
c:\windows\system32, as well. This one has a file size different from
the correct one. Obviously I had started this one (because PATH points
there).
Starting the correct dism.exe let me unmount the WIM without problems.
from:
dism - The directory could not be completely unmounted - process explorer cant find open processes and unmounting fails
Not sure if I should have started fresh this morning or carry on from where we stopped yesterday
I don’t know if it was the commands you asked me to perform yesterday or the fact that explorer was closed (as Jason says was the cause on the link you gave)
But this morning I returned to the rest of the commands (where we left off) and its seems fineJason said:
Not sure:)
Dism not unmounting, seems to be due to having more than one version of Dism on the system - invariably in 64-bit systems, sometimes also can happen in 32-bit with ADK etc. DISM is platform independent - 64-bit Dism can service 32-bit windows and vice versa.
If not specified in the commandline e. g. c:\windows\system32\dism.exe /etc.,but just dism, it may be the 64-bit version in c:\windows\syswow64\dism.exe that actually runs the command, and is involved in an open session with a mounted wim, so when a command to unmount a wim is made, the unoccupied 32-bit version tries to do it and fails, because the other Dism.exe has the mount open. Odd.
But most likely, an explorer window may be the culprit - but it shouldn't hold a file open unless some metadata from the file or folder is in use, such as the properties sheet.
Back to you - it looks like you have successfully added drivers to the image#8 (Pro) in the Install.wim, and unmounted cleanly.
Have you also managed to cleanly unmount the boot.wim image after adding the drivers?
Note that in the run through I did yesterday, I checked the properties of each Wim file before and after adding the drivers to see if the size of the wim had increased.
If so you are ready to go! You could add the contents of C:\ISO to make a bootable USB, as I am sure you have done before, and give it a go at installing.
Of course, there are no guarantees so far, but good luck!
Tried setup from C:\iso file and still froze on windows logo on reboot
Copied the C:\iso contents on to a USB and rebooted, install from USB, froze on windows logo
Going to wipe the hard-disk, re-install 16299 and go through the whole procedure again just to try one last time.
Making a note here for quick reference
----------------------------------------------------------
Create three new files on C:\drive
C:\drivers
C:\iso
C:\mount
Copy the contents of a mounted ISO of Windows 17025 onto C:\iso
Open an elevated command prompt
Export-WindowsDriver -Online -Destination C:\drivers
dism /mount-wim /wimfile:c:\iso\sources\boot.wim /index:2 /mountdir:c:\mount
dism /image:c:\mount /add-driver /Driver:c:\drivers /recurse
dism /unmount-wim /mountdir:c:\mount /commit
dism /Get-WimInfo /WimFile:c:\iso\sources\install.wim
dism /mount-wim /wimfile:c:\iso\sources\install.wim /index:8 /mountdir:c:\mount
dism /image:c:\mount /add-driver /Driver:c:\drivers /recurse
dism /unmount-wim /mountdir:c:\mount /commit
----------------------------------------------------------------
And if that doesn’t work again then I’ll wait till Boxing Day sales and try to get a new motherboard, CPU and ram. :)
Create three new files on C:\drive
C:\drivers
C:\iso
C:\mount
Copy the contents of a mounted ISO of Windows 17025 onto C:\iso
Open elevated powershell
Export-WindowsDriver -Online -Destination C:\drivers
Open an elevated command prompt
dism /mount-wim /wimfile:c:\iso\sources\boot.wim /index:2 /mountdir:c:\mount
dism /image:c:\mount /add-driver /Driver:c:\drivers /recurse
dism /unmount-wim /mountdir:c:\mount /commit
dism /Get-WimInfo /WimFile:c:\iso\sources\install.wimnot needed since we know 8 is the correct image
dism /mount-wim /wimfile:c:\iso\sources\install.wim /index:8 /mountdir:c:\mount
dism /image:c:\mount /add-driver /Driver:c:\drivers /recurse
dism /unmount-wim /mountdir:c:\mount /commit
Quote
