Winpe Dism

[Gaynelle Alnutt]

With a completely fresh Bitdefender Total Security 2016 installation where absolutely NO settings have been changed from their defaults, the above command after taking several minutes returns an error to the effect of "the sources were not available/could not be downloaded".

Unfortunately I have noticed that a corruption occurs after every Windows update with Bitdefender installed and suspect (but cannot be positive) that Bitdefender somehow interferes with the update process and causes the "corruption" which in truth is simply a file mismatch, forcing me to uninstall and reinstall Bitdefender every few days.

Once the installation, activation and update were complete, I re-ran the checks and was again greeted with corruptions that, this time, like mirage22 reported were NOT able to be repaired even after I uninstalled Bitdefender.

After everything else failed and with BitDefender removed from the system, I restored Windows to the previously created Restore Point and re-ran the diagnostics, verifying that the corruption had indeed been repaired (or rather, undone).

Seeing as even the local sources failed to be detected (meaning it was not a connectivity issue), at this point the only assumption I can come to is that, Microsoft must keep separate versions of the files for every Windows build (8, 8.1, 10240 and 10586) and that Bitdefender must mix files intended for the 10240 build in 10586 thus corrupting the identifier and making the DISM command unable to properly detect the correct build in order to download/copy the appropriate files.

*One correction I must make to my previous post is concerning the /Online parameter. The /Online parameter specifies that DISM should target the currently running Windows (the OS that is "online"), as opposed to the /Image: parameter which specifies the path of the Windows being repaired, so that you could for instance connect the hard drive of a non-booting PC to a functioning one to repair it.

For online images, DISM will by default check Microsoft's Windows Update servers for the correct sources. To change that behavior one must specify an alternate source ("/Source") and add the "/limitaccess" parameter, instructing it to ONLY use the specified source.

Attached you will find a zip file (renamed into .log to fool the attachment system) including the SFC (cbs) and DISM (dism) logs detailing all my attempts at repairing the corruption. Hopefully some might be relevant but I must warn you that it includes more than a dozen checks and is rather lengthy.

Concerning the message "The source files could not be found", that could easily be replicated by simply depriving the system access to the "Windows Update" servers since that is what DISM uses by default to get the correct files when using the /online parameter.

which specifically tells DISM to disregard Windows Update and instead get the files from the local "sources" folder failed by returning the exact same error message, prompting me to realize it was not a matter of the command being unable to contact Windows Update but of detecting the correct build in order to fetch the correct files.

One last interesting piece of information is that in one instance I tried to run "System Restore" (RstrUI) with Bitdefender still installed and it failed citing locked access to files from an antivirus program.

Please send us the data requested here if the DISM command still fails with Bitdefender build version 20.0.24.1290 (right click on the B icon from system tray and choose About to see the build number):

I had occasion today to run a "dism" command, as specified (dism /online /cleanup-image /restorehealth). It worked perfectly with the current build of BDTS2016, and fixed the errors that sfc had found. I am really glad that bug has been fixed. Thank you.

3a8082e126