Windows 10: in which folder in wim mounted image added drivers go

I am following a tutorial here to integrate device drives in windows install media, so I mounted the wim file in a directory and I go to see the following directory structure Code: PerfLogs Program Files Program Files (x86) Users Windows Inside them there are several directories and sub directories. I want to know Q1) in which files the drivers I added in this mounted wim folder went. I executed tree /f /a command while on cmd being inside the mount directory but a very big output came on screen. So I am not able to find in which folder the added drivers went. This is a Windows 10 image. Q2) Also I wanted to know will device drivers for Windows 10 work with Windows 11.

:)

 

Windows 10 Upgrade: Stops at 23% without error, Dism not mounting boot.wim WIM Image

If you manage to completely install Windows 10, there are 2 times where Setup counts up in percent.

The first time it counts up, before the reboot, it copies the necessary setup files, and round about 23%, it mounts an image using dism/wim.

Looking at the setup logfile, I saw problems with image mounting.

In my case, the image mounting mechanism was broken, which I verified by copying Windows_10_pro_de_Upgrade.exctracted.iso\sources\boot.wim from the install source folder to C:\temp and then executing

to attempt to mount the image, which failed with error code 87. (Folder C:\Temp\offline has to be manually created. Please note that once you successfully mounted the image, you should unmount it again manually via

)

I could then compare the behavior on the faulty machine to a Win 8.1 Pro VM I had, where the mounting worked. Looking at the Logfile, I noticed that I got a problem with file

Using Sysinternal's Process Monitor I could record dism.exe's actions and compare them to the desired ones. I noticed that the failed action (SetFileSize) occured once in the working mounting case, and twice in the failing one. I looked at the stacktrace of the failing action and saw that there was one additional call, in filter driver cbftlsfs4.sys.





Some googling revealed that this file belongs to Cloudfogger. Uninstalling Cloudfogger (I moved to viivo some time ago after having different issues with Cloudfogger, so uninstalling was no issue) removed both the filter driver as well as the mounting problem.

The Windows 10 upgrade worked afterwards.

Probably, few people have this exact same issue. On a different machine, with an older version of Cloudfogger, I did not have this issue. For me, it was 2 days of work and investigation, and perhaps this is helpful to someone else, so I wrote down my steps in so much detail.

 

how to open wim files

Alright, To mount a WIM file please see this article;

https://www.activedirectory.ncsu.edu/services/i...

Disclaimer:

This is a non-Microsoft website which would provide accurate and safe information. Watch out for ads on the site which are frequently classified as a PUP (Potentially Unwanted Products). There is no need to buy paid products to fix your computers as they do
more harm than good sometimes.

 

Windows 7 embedded .wim image with custom drivers

I'm trying to create a .wim for mass deployment for Windows 7 embedded standard industrial PCs. I have a driver set thats only available via a .exe. These add control panel items. When I run an Unattended sysprep, take an image of the drive, then re
image a new drive with this .wim, that driver and those features are missing. Is there any way to preserve these through a sysprep?