Kindly be advised we cannot cancel subscriptions or issue refunds on the forum.
You may cancel your Bitdefender subscription from Bitdefender Central or by contacting Customer Support at: https://www.bitdefender.com/consumer/support/help/
Thank you for your understanding.
You may cancel your Bitdefender subscription from Bitdefender Central or by contacting Customer Support at: https://www.bitdefender.com/consumer/support/help/
Thank you for your understanding.
Regression Total Security '16 Interferes With Dism /online On Windows 10
Unfortunately there has been a regression with the DISM command when ran under windows with Bitdefender still installed (build 20.0.25.1377).
Bellow is a link to the original thread that was closed just a few days ago.
http://forum.bitdefender.com/index.php?showtopic=67240
Following are the two error codes the DISM and SFC commands return:
PS C:\WINDOWS\system32> dism /online /cleanup-image /restorehealth
Deployment Image Servicing and Management tool
Version: 10.0.10586.0
Image Version: 10.0.10586.0
[==========================100.0%==========================]
Error: 0x800f081f
The source files could not be found.
Use the "Source" option to specify the location of the files that are required to restore the feature. For more information on specify
ing a source location, see http://go.microsoft.com/fwlink/?LinkId=243077.
The DISM log file can be found at C:\WINDOWS\Logs\DISM\dism.log
PS C:\WINDOWS\system32> sfc /scannow
Beginning system scan. This process will take some time.
Beginning verification phase of system scan.
Verification 100% complete.
Windows Resource Protection found corrupt files but was unable to fix some
of them. Details are included in the CBS.Log windir\Logs\CBS\CBS.log. For
example C:\Windows\Logs\CBS\CBS.log. Note that logging is currently not
supported in offline servicing scenarios.
The system file repair changes will take effect after the next reboot.
Attached you will find the DISM and CBS logs from the two commands (just rename the .zip.log file to .zip) and I have also created a BDSP error log which however is too large to attach (39.3MB) so for that I am going to need alternate means of sending it.
/applications/core/interface/file/attachment.php?id=14535" data-fileid="14535" rel="">Logs.zip.log
0
