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

Hi Kzoom,
You ranted out?
Welcome to SevenForums!
You have a few corrupt Winsxs folders
Please download SFCFix.exe to your desktop
Download View attachment SFCFix.zip to your desktop
Drag and Drop SFCFix.zip onto SFCFix.exe
See example <here>
Post SFCFix.txt that will appear on your desktop

Ran it, seems to have finished. Had a couple 'errors'

Stage 1 of 6 failed on server
Stages 2 through 6 seem to have finished. Their notices disappear when they finish.
Then four lines of 'Failed to create zip file with errno 2'


But according to the contents of SFCFix.txt, "Successfully processed all directives."


So I'm going straight to running the Restore, rather than reboot first, since SFCFix.txt says it successfully copied the files specified:
Two locations for TaskEng.exe.mui
One each for netmscli.inf and autochk.exe


Letcha know how it turns out

No luck.


I tried to run RESTORE immediately after SFCFix.exe. Same 'there are corrupted files' pop-up.
I rebooted the machine, tried again, got the same thing.
I reran sfc /scannow, then
: findstr /c:"[SR]" %windir%\logs\cbs\cbs.log >sfcdetails.txt

to get another round of the sfcdetails file, which I'm attaching.,

as well as the SFCFix.txt that the SFCFix.exe generated.



Same three files listed.



And that's it for tonight. 3 hours doing this or waiting for parts to finish.

Still got my work clothes on.

OK,
Please Drag and Drop View attachment SFCFix.zip onto SFCFix.exe
Run sfc /scannow
Run View attachment CBS Log to Desktop.bat
post CBS.log

Thanks for your effort.

I think you're getting somewhere.
The CBS.log doesn't mention autochk or netmscli in the part of the CBS.log that covers this run.
BUT it still calls out the TaskEng as corrupted.
I have not tried a 'Restore', as I figure it'll still complain.

I didn't 'reset' the CBS.log, so it's got leftovers from last night.

It's around 3 mg. (attached)
(Correction, it wouldn't upload. Too big. Truncated version attached, includes ALL of tonight's run.)


NOTE: (And this may be a head slap (for you or you to me)):
I did the plain 'drag n drop' last night, SFCFix.zip onto the exe icon.
Tonight, I right-clicked on the exe's icon, and did 'run as Administrator'. It popped open a command box, gave some 'what to do' instructions, and then said 'press any key to continue'.
Instead, at THIS point, I dragged your SFCFix.zip onto the command window and dropped it.
The exe seemed happy, took it and ran.
I'm attaching its resulting SFCFix.txt too.

Again please
Download View attachment SFCFix.zip to your desktop
Drag and drop onto SFCFix.exe
Run sfc /scannow
Post cbs log

Nite, I have exam in morning!

Ran it twice (got distracted)

I ran your file twice,

'a' by running the exe as Administrator, then dropping your file on the Cmd window,
'b' by simply dragging and droping your file onto that exe's icon.
The sfcdetail for each run is also attached,

as well as a truncated CBS log.



Hope the exam went well.


Thanks for your efforts.

Exam, I believe, went well.
Having trouble finding the correct files (hash match)

May just throw in the towel

Glad to hear the exam went OK.



I've got stuff to do in my evenings and through the weekend.
I may just throw in the towel and reimage from my most recent backup. And it's from last weekend.


May give upgrading to Win 10 another try, too.


Thanks for the effort.

I'm installing Win7x64 Pro with all updates on External HDD. I'm thinking that may produce the dll files with the correct hash that matches your files.


Have you considered a Repair Install/ In-Place Upgrade? It replaces your OS, keeps everything else and makes a backup, windows.old.
Here's the scoop View attachment Repair Install Instructions.docx

Backup is screwed, too

(Posted this to Synology Support last night)


Thoroughly screwed. Windows Update KB4493472 killed the mappings on my Win7ProSP1 64bit to my DS212. (Can connect to my router though.)
Windows Restore suddenly won't work due to 3 corrupt files.
Spent a week online at sevenforums.com with sfc and sfcfix trying to solve. No luck.

(Update KB4493472 killed local network connection, now can't RESTORE)



Faithfully running Acronis backups, saving to DS212, and Hyper Backup on NAS faithfully writing out to an ioSafe USB drive.

Fine, I'll just hook the USB drive up to the Win7 PC, do a full restore from that.



"Drive is not Formatted. Do you want to Format now?"

Oh, right, a Windows-unreadable format was recommended for the USB drive hanging off the NAS for backups.


How about a direct network connection from the NAS to the PC, skipping the intervening router?

NAS wants an IP address, PC doesn't have a DHCP service, and I'm incredibly reluctant to screw up my local network connectivity, for fear of not being able to send you this trouble ticket.

So no direct connect to the NAS.



Yes, I can see it through my No-IP connection, but I don't want to try to do a Restore of around 250G through a website connection, even if it was possible. It'd take two weeks.



So, as I said at the top, I'm screwed.
No way to connect to the NAS, no way to read the USB drive from PC, so no way to do the restore, which is the WHOLE POINT to doing backups.



But I've sure learned the weaknesses in my multiple redundancy backups. If I get out of this without erasing my drive back to baseline Lenovo Recovery Win 7, I'm redesigning my whole backup process, and I'm reformatting the USB to a Windows-readable format, regardless of speed.
There has to be a format that the NAS will write to, and Microsoft can read.

Spent this evening with a connectivity method Synology handed me on a Support Ticket. Got me within a few feet of connected, but not quite there. Could See the NAS as a media device, and Winodws Media Player could play the music on it. Could see the NAS's web-site at 169.254.0.1:5000 after doing a manual IP address for the PC, and running the vendor's Connection assistant.
But never could see it as files in Windows File Explorer, so can't do a Restore from my Acronis backups.


Won't be able to get back to this before Monday, other than to read the instructions at the link in your last post.



Great way to spend my evenings...and yours. Thanks, Microsoft.

Status: NAS is again connected to outside world (No-IP redirect) and to the local network (wife's hard-wired Dell PC), but still can't be seen from my Windows 7Pro PC.

Acronis backup has not succeeded. First run hung at 'Loading...' black screen during reboot, for three days while I was gone. 3-finger salute resulted in 'corrupted disk' that took Windows twelve hours to chkdisk before allowing a reboot.
I spent one evening since trying to do the Acronis restore, both attempts taking less than 5 minutes, neither resulting in a Restore or a new connection.
Opened a ticket at Acronis, so now I have three+ open. One here, one there, and one at Synology, maker of the NAS.



If anyone can recommend a reputable network jock who'd like a shot at fixing this network connection by remoting in, I'm open to the idea.

How's that for a desperate plea? Yikes.



Bottom line: I will NEVER do another Windows Update again. Cause that's how I got in this mess.

Well, Acronis Restore has failed, too.

I'm still screwed. Been trouble-shooting with Acronis, as their recovery software is not, well,...recovering. May actually take a day off this week, as my job is 8-5 plus commute, and their paid phone support is only 9-4,M-F

Meanwhile, here's a couple of challenges:
1) These three Windows Update each caused my PC to lose the connection to my local network, (NOT the internet.)
KB4457144
KB4343900
KB4493472

Now if anyone can see what's common among those three, but not in any Updates prior to those, I'd appreciate that analysis. The first two I did on 1/22/18, the third I did on 4/27/19. I did all of them well after they were issued, because of this issue and the need to roll back is this disconnect happened. the restore didn't work the last time.

2) I read somewhere about SMB(?) 1 2 3 issues, that MS was discontinuing(?) the use of one of these. If anyone has any ideas on how to verify the settings on my PC, and any/all other h/w in the home network, back to the NAS, I'd appreciate it.

FWIW, I've reported all this fun to Acronis, Synology, and here (as a better source than Microsoft.) I'm about ready to do a paid call to Microsoft, if such is possible.

Thanks for reading this far. Just a message in a (disconnected) bottle.


Kelley