Six weeks after first release of build 1809, and Redmond still can’t get it right
The 1809 build of Windows 10 and Windows Server is fast becoming infamous. Microsoft pulled it shortly after release when it started deleting people’s files, and stumbling in other ways. Redmond reissued the software on Tuesday, and today it’s clear you shouldn’t rush into deploying it, if installing it at all, in its present state.
Buried among the release notes for the re-released build is this little advisory, in which Microsoft admits:
We can imagine that being a little annoying for people in work environments or otherwise relying on network shares.
Microsoft does provide a number of possible workarounds for the loss of network drive connectivity – a bug it knew was present in build 1809 of Windows, but chose not to fix in the re-release. It suggests setting up script files, scheduled tasks, or changing group policy settings.
