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

(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.

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