It appears something was changed by update (rollup) KB4015549 that caused the "could not reconnect all network shares" issue to happen, or worsen. Has anyone else noticed this? Or thinks I'm barking up the wrong postman? Long story short: I installed a new PC (HP 800G2 Mini) with Windows 7x64 Ultimate two months ago. At the time, I used the Simplix* pack from February to update the clean SP1 install. At first I got the "could not reconnect all network drives' issue but by the time I had finished my setup and changed the network startup policy, the issue was resolved. The PC hasn't had that issue since then, until... I updated from April's Simplix pack (17.4.20) a few days ago, and on reboot the "could not reconnect..." issue started. It happened every startup since then - about ten times without fail. Only three updates were listed in in 'programs and features/updates' from that update. The other two looked innocuous so I uninstalled KB4015549. Since then, I've started up about five times without the "could not reconnect..." issue. So, it looks like something in KB4015549 is the culprit. I have a couple of startup programs that get upset if Windows tells them there is no mapped network drive, so I'm sensitive to this issue. At the moment I'm torn between wondering if I really need the update for some security hole, and having my PC work the way it should. I hate Microsoft! * I don't mean in any way to imply this problem is caused by the Simplix pack itself - it's a wonderful tool!