After a lot of chaos and problems, Microsoft has resumed the Windows 10 1809 rollout. While the recent October update fixes some reported bugs, it still has some problems. Reportedly, the new rollout has brought back an old vulnerability in file explorer regarding mapped drives.
File Explorer Flaw In Re-Released Windows 10 1809 Rollout
While the re-released Windows 10 1809 rollout fixes bugs like auto-file deletion, it brought back another problem reported a month ago. The vulnerability exists in the File Explorer that shows mapped network drives as being broken despite functioning normally.
The File Explorer bug was first pointed out on the Microsoft tech network in a question:
“Testing the new 1809 update, and everything seems to be fine except all mapped drives to Windows 2012 file servers show disconnected (red x) after reboots or logoff/on. Everything is fine if user opens the mapped drive. This causes problems when user opens a file located in map drive A but links to another file in mapped drive B. Anyone running into the same issue?”
After his question, several other users confirmed the existence of the glitch.
Now that more than a month has already passed, this particular File Explorer problem remains unpatched. Even the recently re-released Windows 10 October update didn’t patch the flaw. Microsoft also acknowledged this error for which it has recommended workaround. As described,
“You can work around this issue by running scripts to automatically reconnect mapped network drive when you log on the device. To do this, create two script files, and then use one of the workarounds, as appropriate.”
More Windows 10 1809 Update Issues
In addition, the recent Windows 10 update also exhibits compatibility issues with Trend Micro’s OfficeScan and Worry-Free Business Security software. Until a patch is available, Microsoft has allegedly blocked the devices from receiving Windows 10 1809 update.
Moreover, this update also causes Microsoft Edge tabs to crash as AMD does not support the Radeon HD2000 and HD4000 series. This bug also awaits a patch from Microsoft. Nonetheless, until Microsoft mitigates the matter, they have blocked the devices running these GPUs from receiving the Windows 10 1809 update as a workaround.
Take your time to comment on this article.