Windows Home Premium 7 SP1, x64
Updates KB3004375 & KB3031432 won't install and give me error code 80083712
Did run SFC/scannow and also Disk Error Check both of which completed their work.
Have also run Windows Update Diagnostic.diagcab
Hope you can help on this.
Thanks
CheckSUR shows this problem
I'll post a fix when I can get through the backlog!Code:Unavailable repair files: winsxs\manifests\wow64_microsoft-windows-systemrestore-main_31bf3856ad364e35_6.1.7601.18741_none_af36fc0afe5a6622.manifest
I've uploaded a file - dhhaa.zip - to my OneDrive at Noel's OneDrive
Please download and save it.
Right-click on the downloaded file, and select Extract all…
Extract to the default location - which will create a new folder dhhaa in the same place.
Open this folder - there should be one folders inside it (Manifests,)
Copy the content of the manifests folder (.manifest files) into this folder:
C:\Windows\Temp\CheckSur\Winsxs\Manifests
Now run the CheckSUR tool again (it may take a while)
Post the new CheckSUR.log file, and the CheckSUR.persist.log file.
@NoelDP I had the updates on the desktop, and now they've both installed and going to Windows Update I got the all clear.
Thanks so much for your help, be badly stuck if people like you weren't here to clean up these loose ends that MS leaves hanging.
Thanks
The problem arises mostly because of the billions (literally) of potential hardware configurations, and the freedom with which people can install almost anything (unlike in the Mac world, where installation of almost anything is impossible unless it's been 'approved' [and paid for] ).
Any system as complex as an OS is, is going to be subject to problems - ranging from hardware failure, through system bugs, to inept programming and malware - and nothing will ever change that. The MS success rate is actually surprisingly high, considering, and it's only the outliers that end up with 'insoluble problems' which are in reality insoluble only because it's not economically viable to fix them unless they affect a large number of people. It's the law of supply and demand in its raw form - if enough people have a particular problem, MS will fix it (in your case, with CheckSUR). If MS don't fix it, it's left to people such as me to provide support until they do, or until the OS dies of old age. Every few months MS add files to the CheckSUR capability - how long that situation will continue is debatable, but one would hope that it will be until at least 2019, when Win7 goes official out of support.
@NoelDP ,Thanks again for the fix, and explanation;
BUT M$ did not fix it with CheckSUR, You fixed it.
Ah - but when MS revise CheckSUR next time, it may have the fix
Glad it worked for you... Good luck!
Quote