New
#1
Update KB4493472 killed local network connection, now can't RESTORE
(This will be a vent and an 'ask' for technical advice.)
I regret doing Windows Updates.
I have a couple of PCs, including this Thinkpad running Win7ProSP1 64bit.
I keep all the photos and music files on a local Synology NAS, with mapped drive designations (\P for Photos, \M for music, etc....)
I also have a regular backup running on these PCs, which saves the backups to that NAS, again to a mapped drive.
Got it?
I turned off 'Auto Update' for Windows a while back, because every once in a while, some Update would kill this PC's connections to these mapped drives. I can still get to the internet, just can't see those drives. Which also kills the backup's ability to write out the backup files.
So I now do the updates manually, one at a time, checking after a reboot that I still have connectivity.
When I don't, I mark that update as 'bad' (at least for me), skip it, and do a RESTORE.
Worked fine until yesterday.
I ran the Updates, one at a time, on
2018-12 (KB4483187)
2019-02 (description too long to read KB##)
2019-03 (KB4474419)
and these all still left me with connectivity.
This is a pita, because the reboot on Win7 takes too damned long, which is why I have 24+ updates of various "Importance" to do.
Next I did 2019-04 Security Monthly Quality Rollup for Windows 7 for x64-based systems
This was KB4493472.
And my connectivity went a-w-a-y...
OK, run a RESTORE, and...
Nope, first time ever, I get this error, a pop-up announcing:
"Windows has detected file system corruption on Windows7_OS (C:).
You must check the disk for errors before it can be restored."
So my search landed me at sevenforums.com, on a tutorial on running SFC /scannow
SFC /SCANNOW Command - System File Checker
(which you'll notice is 97 pages long, so I've not read it all, but...)
This fixed one of the four files it claimed are corrupted, wmiutils.dll.mui. ('mui'?)
But I still need to fix:
autochk.exe
netmscli.inf
TaskEng.exe.mui
All of these show "hash mismatch" errors, apparently between the hash on the corrupted versions and on the recoverable versions out the those damned WinSxS files that take up so much room, yet are useless in this case.
I've run sfc /scannow three-four times, as recommended in 'brink' s tutorial (above), and have run into this wall.
I do not want to do a clean re-install (who does?).
Never used the image of the vendor's install that I assume is on the local "Q: Lenovo_Recovery" drive. So I'll look at using that to recover 'valid' versions of these files.
If all else fails, I'll drag out the back-up drive that the NAS backs up to, and plug it directly into this Thinkpad, and do a reinstall form the latest Full + differential.
And NEVER do another Windows Update again.
I'm attaching the sfcdetails.txt file that's the distillation of sfc's CBS.log.
If anyone has a better solution, or a reputable utility that might fix this, I'll give it a try.
Two side notes, for anyone who'd really like to get into the weeds on this:
1) Back in mid-October 2018, I read that my connectivity issue might be a mismatch of support on network SMB protocols (MS had apparent;y dropped support for SMB1 (?)). So I upgraded the NAS to SMB 2. Didn't hurt, but didn't solve the issue.
2) And the two Updates that caused issues back then were:
2018-08 Security Monthly Quality Rollup for Windows 7 for x64-based systems (KB4343900)
2018-09 Security Monthly Quality Rollup for Windows 7 for x64-based systems (KB4457144)
Wow, I sure enjoyed spending Saturday night and most of a sunny Sunday in a dark room chasing this bug, a "one-time learn" that makes my brain hurt more than my job does.
Oh, and for the "just upgrade to 10" solution, the graphic card inboard on this isn't supported. Tried twice. Already have a new SurfacePro 6, but this Thinkpad is the home base.
Wasn't planning on tossing it for another year or so.
Gonna go see daylight for a bit. Thanks for reading this far. You get it.
~~~~~~~
Sheriff Bart: "Do you need any help?
Waco Kid: "Oh...all I can get."
- Blazing Saddles, 1975