Windows 10: I've been having problems with my driver and the scf or dism are not working

Hello, when I run the Dism this is what I get. All the help will be very usefull. Plus every time I boot, after a while I get the message "restart to repair drive errors". Hopefully you can help me out

2020-11-26 16:12:01, Info CSI 00000223 [SR] Cannot repair member file [l:12]'uaspstor.inf' of dual_uaspstor.inf, version 10.0.19041.1, arch amd64, nonSxS, pkt {l:8 b:31bf3856ad364e35}, type [l:14]'dualModeDriver' in the store, file is missing

2020-11-26 16:12:01, Info CSI 00000224 [SR] Cannot repair member file [l:8]'uefi.inf' of dual_uefi.inf, version 10.0.19041.1, arch amd64, nonSxS, pkt {l:8 b:31bf3856ad364e35}, type [l:14]'dualModeDriver' in the store, file is missing

2020-11-26 16:12:01, Info CSI 00000225 [SR] Cannot repair member file [l:49]'3803E232ACAB2476E81BC8A88D5B231A677DA3BC\uefi.inf' of dual_uefi.inf, version 10.0.19041.1, arch amd64, nonSxS, pkt {l:8 b:31bf3856ad364e35}, type [l:14]'dualModeDriver' in the store, file is missing

2020-11-26 16:12:01, Info CSI 00000226 [SR] Cannot repair member file [l:12]'uaspstor.inf' of dual_uaspstor.inf, version 10.0.19041.1, arch amd64, nonSxS, pkt {l:8 b:31bf3856ad364e35}, type [l:14]'dualModeDriver' in the store, file is missing

2020-11-26 16:12:01, Info CSI 00000227 [SR] This component was referenced by [l:157]'Microsoft-Windows-Client-Desktop-Required-Package0110~31bf3856ad364e35~amd64~~10.0.19041.610.46D01845C9C60659D1B4D1712CA91DD7ECF79BCF1E42397337A1284E9FCEBD76'

2020-11-26 16:12:01, Info CSI 00000228 [SR] Cannot repair member file [l:8]'uefi.inf' of dual_uefi.inf, version 10.0.19041.1, arch amd64, nonSxS, pkt {l:8 b:31bf3856ad364e35}, type [l:14]'dualModeDriver' in the store, file is missing

2020-11-26 16:12:01, Info CSI 00000229 [SR] This component was referenced by [l:157]'Microsoft-Windows-Client-Desktop-Required-Package0110~31bf3856ad364e35~amd64~~10.0.19041.610.C280F498ECD1F7B272803E71D67F16B5ADB8EC5E8C4634F1CD38A70C2404A648'

2020-11-26 16:12:01, Info CSI 0000022a [SR] Cannot repair member file [l:49]'3803E232ACAB2476E81BC8A88D5B231A677DA3BC\uefi.inf' of dual_uefi.inf, version 10.0.19041.1, arch amd64, nonSxS, pkt {l:8 b:31bf3856ad364e35}, type [l:14]'dualModeDriver' in the store, file is missing

2020-11-26 16:12:01, Info CSI 0000022b [SR] This component was referenced by [l:157]'Microsoft-Windows-Client-Desktop-Required-Package0110~31bf3856ad364e35~amd64~~10.0.19041.610.C280F498ECD1F7B272803E71D67F16B5ADB8EC5E8C4634F1CD38A70C2404A648'

:)

 

How to get damn DISM to work?

Thx guys, I'll compress this data into a blog post. For all the so called guides I've read, not a single one mentioned it has to be WIM file (some listed even ESD which clearly doesn't work) or that certain ISO images don't work with DISM.

After I've done DISM thingie, SFC also managed to repair stuff. Which is what I've needed here.

 

Programs not working

In post 26 there were steps listed to fix the operating system corruption.
Are you able to follow them?
In post 29 was the suggested dism repair command.

 

DISM - Add or Remove Drivers on an Offline Image


Ah I thought you might be doing the DISM/drivers one.

It is good info and I use parts of this frequently when I'm reinstalling on my old hardware and need to manually add drivers.

I would suggest DISM /Get-Drivers as an alternate to the Powershell step in 2.2 - the table format is quite useful I find.

One method of applying the drivers I tried which seems to work (not sure how valid it is) when clean-installing a machine as a one-off:

1. Export drivers as per Step 2
2. Use DISM /Get-Drivers to show which driver is which, and copy only the ones I know are problematic to a subfolder, and add this subfolder to a bootable Windows 10 Setup USB
3. Boot Windows 10 Setup from the USB
4. Open a command prompt with Shift F10, type command 'wpeutil shutdown' but don't press enter. Instead, Alt-Tab back to Setup
5. Follow the normal clean install process, delete partitions and let it install the relevant edition
6. When it says Restarting in a few seconds, quickly Alt-Tab to the command prompt and press enter, to stop it restarting but shut down instead
7. Boot again from the USB, go straight into Shift-F10, and use DISM /add-driver to add relevant drivers to the offline Windows drive as per Step 4
8. wpeutil shutdown again, and let it restart this time, so that Windows boots and finishes configuring itself with the new drivers available to it.

I found it easier than Mounting the image and also means I don't change the .WIM so I can use that on other hardware without fear of non-standard (and probably quite old) drivers getting in the way .

Although in some cases I could install and change it once Windows is up and running , one of 1709's default drivers causes a BSOD during installation itself, if I don't add the alternative manually using the above technique before it gets to that point.

But it's not a technique I've seen anywhere else so I'm probably bending the rules somewhere. *Wink