Hello, I'm here to report that I have some OS issues with two computers that I have.
The first one I've got OS issues with, is the HP ProDesk desktop which I've had for a few years now. But way back around 2013, the memory modules in it became faulty (possibly due to ESD damage, back when I wasn't good at knowing how to handle things with care). Because I'm now experienced, use anti-static equipment connected to an earth point, and have learned a lot since then. And I replaced the memory modules as soon as those BSOD errors, along with the memtest software started showing errors.
But after I fixed that issue back in 2013 and had no more BSOD errors, I noticed that the Windows Update files became corrupt, along with IE itself somehow got deleted from the memory errors during that time (never used that web browser anyways). DISM returns with error 87 and saying that the cleanup-image option is unknown:
Code:
C:\Users\Administrator>dism /online /cleanup-image /scanhealth
Deployment Image Servicing and Management tool
Version: 6.1.7600.16385
Image Version: 6.1.7601.18489
Error: 87
The cleanup-image option is unknown.
For more information, refer to the help by running DISM.exe /?.
The DISM log file can be found at C:\windows\Logs\DISM\dism.log
SFC returns with saying this:
Code:
C:\Users\Administrator>sfc /scannow
Beginning system scan. This process will take some time.
Windows Resource Protection could not perform the requested operation.
Upon reading the dism.log, I noticed there was some errors and warnings such as this
Code:
2017-04-02 00:27:37, Warning DISM DISM Provider Store: PID=1136 Failed to Load the provider: C:\Users\ADMINI~1\AppData\Local\Temp\6B597148-EF5E-4825-B7B1-792A8520BD75\PEProvider.dll. - CDISMProviderStore::Internal_GetProvider(hr:0x8007007e)
or these:
Code:
2017-04-02 00:27:44, Error DISM DISM Package Manager: PID=1136 Failed initializing the session. - CDISMPackageManager::RefreshInstanceAndLock(hr:0x80070246)
2017-04-02 00:27:44, Error DISM DISM Package Manager: PID=1136 Failed doing internal initialization - CDISMPackageManager::Initialize(hr:0x80070246)
2017-04-02 00:27:44, Warning DISM DISM Provider Store: PID=1136 Failed to call Initialize method on IDismServicingProvider Interface - CDISMProviderStore::Internal_LoadProvider(hr:0x80070246)
2017-04-02 00:27:44, Warning DISM DISM Provider Store: PID=1136 Failed to Load the provider: C:\Users\ADMINI~1\AppData\Local\Temp\6B597148-EF5E-4825-B7B1-792A8520BD75\CbsProvider.dll. - CDISMProviderStore::Internal_GetProvider(hr:0x80070246)
I may have learned a lot from my course, but that doesn't mean that I still have a lot to learn. Anyways, checking the CBS.log file shows quite a lot of errors in it. For one, I've noticed there's STATUS_ILLEGAL_CHARACTER in the one of the errors, as seen here:
Code:
2017-03-27 12:25:50, Error CSI 00000005@2017/3/27:01:25:50.973 (F) d:\win7sp1_gdr\base\lstring\lblob.cpp(2221): Error STATUS_ILLEGAL_CHARACTER originated in function RtlTranscodeLBlobs expression: __rv.UcsCharacter != (0xffffffff)
And here's the thing, I even used SFCFix from here on Sysnative, it couldn't do anything to fix any of the SFC errors. From what it's shown, there's some unicode corruptions.
If anyone wants to take a look into my logs, here they are:
View attachment logs.zip
Just keep in mind that CheckSUR.log and CheckSUR.persistent.log are from way back in 2014, so they would not be relivent to what is happening right now, but it could come in handy if anyone wants to find out what the issue is.
Also, in the past, I have tried booted into safe mode, tried using a repair install (which failed with some error that I can't remember well, but seemed to be because it wasn't an HP OEM disc, which doesn't exist at all for HP ProDesk). I have also tried running sfc /scannow using the Windows 7 ISO image I've used, which resulted in it saying that it will run after rebooting Windows, which doesn't happen. I've also tried using DISM using the ISO image, but it resulted in the same error 87 that I get from when I use it when running from the system itself.
So yeah, I'm actually curious on how I can replace any of the corrupt files, including registry files, and which ones to replace and how to find new ones. This is something I probably have not learned yet, but I am willing to learn how to find and detect such files.
