قالب وردپرس درنا توس
Home / Tips and Tricks / Windows 10 October 2018 Update Breaks Mapped Network Drives

Windows 10 October 2018 Update Breaks Mapped Network Drives



Microsoft's October 2018 update is largely over, but there are still some long-standing bugs. Microsoft has confirmed an issue where mapped network devices are broken after a computer has restarted. This will not be resolved until 2019.

Liam Tung covers this issue at ZDNet:

Within a few days after Microsoft's first release of Windows 1

0 1809 in early October, IT professionals noted that Windows File Explorer indicated foldering network Drivers turned out to be broken.

"Testing the new 1809 update, and everything seems good except that all mapped devices to Windows 2012 file servers display disconnected (red x) after restart or logging / on", wrote an IT professional on October 5th, with many others who confirm the same issue on corporate networks.

"All is good if the user opens the mapped device. This causes problems when the user opens a file located in folder A but links to another file in mapped device B."

Mapped network devices are used primarily on the domain and others big networks, so this is not a problem as the average home user is likely to notice.

Microsoft has acknowledged the problem and provided some suggestions for solutions. The Windows 10 version 1809 status computer says "Microsoft is working on a resolution and will provide updates in the 2019 timeframe."

RELATED: Windows October 10 update returns, promises not to delete your files [19659010] Trend Micro and AMD Radeon Problem

The October 2018 update has some further issues that Microsoft has now recognized.

This update has a "compatibility issue" with Trend Micros OfficeScan and Worry Free Business Security software. This version of Windows requires antivirus software to use a "secure process" for security, so Trend Micro is likely to not get the job done on time. Operating system updates are blocked on devices running this software until Trend Micro expires as a patch.

There is also a problem with AMD Radeon HD2000 and HD4000 GPU systems. Microsoft Edge may stop working with systems with these graphics processors. The lock screen may not work well, and you may receive an error code "INVALID_POINTER_READ_c0000005_atidxx64.dll". Microsoft has blocked updates on computers with this hardware while it displays a solution. AMD no longer supports these graphics processors, so Microsoft has to solve the problem.

The Trend Micro issue is Trend Micro's error, so Microsoft can not really be blamed for it. The AMD Radeon problem sounds like AMD's error, but AMD no longer supports that hardware so Microsoft has to fix the problem on its own. Again, this demonstrates the challenge of "Windows as a Service."


Source link