Windows 10 KB4487181 fixes GSOD errors and USB lock issues

by Milan Stanojevic
Milan Stanojevic
Milan Stanojevic
Windows & Software Expert
Milan has been enthusiastic about PCs ever since his childhood days, and this led him to take interest in all PC-related technologies. Before joining WindowsReport, he worked as... read more
Affiliate Disclosure
windows 10 update

Microsoft released a new Windows 10 cumulative update: KB4487181. The big M added three bug fixes aimed at solving frequent issues reported by Insiders.

Notably, only the Fast ring insiders have access to the newest build. Those who either prefer to use stable builds or are on the Slow Ring will have to wait for Microsoft to release a build for those specific channels.

Furthermore, those users who are eligible for the update will automatically receive the latest build. Of course, you can also use the Updates & Security section that is available within the settings menu to download the update manually. The Microsoft Update Catalog website allows the IT administrators to download the update directly from the official Microsoft website.

The reliability of the  Windows 10 cumulative update seems to be significantly improved by Microsoft due to the following reasons:

  • No failed installs have been reported yet
  • There is a significant decrease in the number of similar issues during the past few months

What does KB4487181 fix?

The following fixes have been done in the latest release:

  • Unexpected lock while ejecting the USB 

When a user tries to safely eject a USB the unexpected lock will not be applied by the File Explorer.

  • The unlock hanging issue

AD users will no longer have to face the next unlock hanging issue as a result of the password change.

  • Frequent bugchecks (GSODs)

The issue related to the frequent bugchecks (GSODs) in the last two flights has been resolved in this build.

This Windows 10 cumulative update has three main issues that have been confirmed by users. The update has inherited these issues from its predecessors.

Microsoft indicated the resolution of these bugs in the upcoming releases but an ETA has not yet been shared.