Microsoft Fixes Long-Time File Explorer Bugs in Latest Windows 10 Update

The most recent optional cumulative update shipped by Microsoft for Windows 10 version 1903 and Windows 10 version 1909 resolves a number of long-time File Explorer bugs, as well as other issues reported in the previous months.

Windows 10 cumulative update KB4532695, which is available for both OS versions, fixes an element that blocked pasting in the File Explorer search bar using the right-click button. This is a bug that was first discovered in Windows 10 version 1909 (Windows 10 November 2019 Update) soon after the debut of this feature update.

Additionally, the same update also includes additional fixes for the search bar, as some users complained of a freezing issue when clicking it. Microsoft states that it resolved a glitch preventing the search bar from “receiving user input,” so everything should work effectively after installing KB4532695.

The gray box that shows up when searching in File Explorer has additionally been corrected, Microsoft says. A similar problem affected the classic Control Panel, which a person resolved too.

Windows Hello improvements

Today’s update also comes with refinements for Windows Hello, the biometric authentication system available in Windows 10. Microsoft says it has implemented a series of improvements for that accuracy of Windows Hello face authentication.

The Start menu gets its own tweaks today, so after installing the cumulative update, the problem changing the user-customized order of live tiles even if the layout is locked should no longer occur. Unplugging a USB Type-C flash drive should stop returning an error, Microsoft says.

This cumulative update is available being an optional patch in Windows Update. All improvements that are included here will also be area of the next Windows 10 cumulative updates going survive the February patching cycle. The upcoming Patch Tuesday takes place last month 11.

Microsoft Releases Windows 10 Version 1909 on Update Assistant

Microsoft announced Windows 10 version 1909, or Windows 10 November 2019 Update, earlier this year, however the automatic rollout hasn’t yet started and users can only download the brand new feature update on compatible devices with a manual check for updates on Windows Update.

Today, however, Microsoft is providing users with yet another option as well as the three ways to download Windows 10 version 1909 that we’ve already described at length here.

The Windows Update Assistant now serves the November update too, so devices still running Windows 10 version 1903, or Windows 10 May 2019 Update, can use this tool to easily install the brand new release.

Manual check for updates

Obviously, the Update Assistant still performs a number of checks on your device, so should any compatibility problems be found, the new feature update may not be offered. This means you can always have to turn to other methods of installing the November update, albeit bypassing the safeguard holds isn’t recommended because of the bugs you could experience.

While using Update Assistant is simple as pie, because the whole thing was developed as a wizard, and therefore you simply need to consume a few steps to complete the upgrade process. Obviously, it might take a while before the system is update because of the size of the update.

In case your device is unlikely to experience any issues with the November update, then your most simple way to download the new feature update may be the manual check in Windows Update. Microsoft has released the update for seekers, which allows users who execute a manual look for updates on their devices ought to be offered Windows 10 version 1909 if no risk of hardware or software compatibility issues is determined.

The rollout to devices across the world will continue within the coming weeks according to Microsoft’s gradual release approach.

Microsoft Enables Automatic Upgrades on Windows 10 Version 1803

Devices running Windows 10 version 1803, or April 2018 Update, will be automatically upgraded to a newer version of Windows 10, Microsoft says.

Launched at the begining of 2018, Windows 10 version 1803 reached the end of support for Home and Pro SKUs on November 12, and Microsoft warns that upgrading to a newer version of the operating system is the only way to carry on to receive security updates.

Microsoft also launched Windows 10 version 1909, also referred to as November 2019 Update, earlier this year. The organization, however, didn’t mention the version that Windows 10 version 1803 products are upgraded to, albeit there’s an opportunity that for the moment, it uses Windows 10 version 1903 (May 2019 Update) as the preferred choice for scalping strategies.

Users permitted to choose when you should install the update

Windows 10 version 1909 is still in the early days, and Microsoft is still working on determining its reliability having a gradual rollout system. The upgrade is available just for users who manually check for updates in Windows Update.

“Windows 10, version 1803 (the April 2018 Update) Home and Pro editions reach end of service. For Windows 10 devices that are at, or within several months of reaching end and services information, Windows Update will automatically initiate an element update (with users having the ability to select a convenient time); keeping those devices supported and finding the monthly updates that are important to device security and ecosystem health,” Microsoft explains.

Microsoft emphasizes that users it’s still permitted to choose when you should reboot their devices to install the newer Windows 10 version, that ought to technically assist in preventing unexpected reboots.

Windows 10 version 1803 has long been the number one Windows 10 release, but based on third-party data, the May 2019 Update has already secured the leading place.

Windows 10 Cumulative Update KB4515384 Now Said to Break Down PIN Logins

The September 2019 cumulative update for Windows 10 is quickly being a huge fiasco, as at least one of the patches that Microsoft shipped this month keeps causing one issue after another.

This time, a report from AskWoody indicates that cumulative update KB4515384 stops working the PIN login system on devices running Windows 10 version 1903, or Windows 10 May 2019 Update.

For now, this doesn’t appear to be a widespread problem, but a person report cited through the linked source suggests that out of 4 systems, at least 3 encountered the bug.

Initially, the only workaround appears to involve deleting the contents of the NGC folder, which holds all settings associated with the PIN system.

“Delete the items in the folder C:\ Windows\ ServiceProfile\ LocalServices\ AppData\ Local\ Microsoft\ Ngc , then reboot, and your prompted for that Pin login again. Don’t know why it’s requiring a 6 digit PIN, because I’ve never set that rule. The files in the Ngc folder is going to be rebuilt whenever you reboot,” one user is cited as saying.

Old issue, new problems

As Woody Leonhard notes, this isn’t necessarily a brand new bug, albeit showing up once more in September is unquestionably unexpected.

Microsoft delivered a fix in the late-August cumulative update KB4512941 to correct the error wearing down the PIN system, but at this time, it’s not known when the two are related or this can be a new problem in Windows 10 version 1903.

“Addresses an issue that prevents the personal identification number (PIN) prompt from appearing when authenticating in Internet Explorer,” Microsoft said in the release notes from the August update.

Microsoft is yet to understand the bug within this new cumulative update, so for the time being, we still don’t have a confirmation if this sounds like a problem that could hit others or only an isolated report.

What’s New in Windows 10 Cumulative Update KB4515384 for Version 1903

The September 2019 Patch Tuesday rollout also includes a cumulative update for Windows 10 May 2019 Update, or Windows 10 version 1903 as Microsoft calls it.

The cumulative update under consideration is KB4515384, and the first change that it produces on the device where it’s installed is definitely an increase of the OS build number to 18362.356,

You are able to determine the OS build by clicking the beginning menu and typing winver.

Such as the other cumulative updates published on Patch Tuesday, KB4515384 comes with both security and non-security improvements, and one of the most notable concerns protections from the speculative execution side-channel vulnerabilities known as Microarchitectural Data Sampling and affecting 32-bit versions of Windows.

Moreover, this update fixes our prime CPU usage bug in Cortana, whilst sporting refinements for Edge, Internet Explorer, the Microsoft Scripting Engine, Windows Authentication, along with other Windows components.

No known issues

Microsoft says the same cumulative update includes improvements for verifying passwords, but in addition for storing and managing files.

There are no known issues within this cumulative update, and this is definitely the best thing because of the issues that so many users encountered in the past after Patch Tuesday rollouts.

You should check out the entire changelog in the box following the jump.

Windows 10 version 1903 is easily the most recent stable form of the operating-system, with another feature update ready for the fall of this season. Specifics on if this version is projected to start rolling to users continue to be not available.

On the other hand, version 1903 is still while being pushed to devices in stages, as Microsoft embraced a more cautious update for this release. The update, however, can be downloaded by anyone from Windows Update using a manual look for updates on the Windows 10 device.

How to Automatically Restart Your Device After Installing Windows Updates

Installing Windows updates is a vital thing for each and every one of us on Windows, as they include not only further refinements for the operating-system, but also critical security fixes that can protect our data against cyberattacks.

Updating Windows, however, is definitely a crazy rollercoaster ride for users worldwide, because the overall experience has often been ruined by both surprise behavior along with a bad approach implemented at OS level.

While botched updates still happen every once in a while, long-time Windows users certainly remember the instances when the operating-system restarted out of the blue to complete the update process.

Microsoft has since tried to address these complaints, and at this time, users are supplied by having an additional group of controls to ensure everything regarding the update from the system works as expected.

Recently, however, some IT admins told me that although the forced reboots to complete updates was annoying at times, they were a necessary evil. Mostly because some people within their organizations never manually reboot their devices to set up updates, so despite the patches actually being there, they become pushed back, leaving the unit all susceptible to attacks.

Windows 10 version 1903 comes with a dedicated option that addresses this issue and allows a pc to be configured to automatically reboot after installing updates.

First and foremost, what’s very important to know is that this option comes disabled automatically. This means that devices shouldn’t normally try to reboot after installing Windows updates, and this is clearly the right approach given all the criticism in the past years.

The option is situated at the following path fitted 10 device:

Windows 10 > Settings > Update & Security > Windows Update > Advanced options

And it’s called:
Restart this product as quickly as possible when a restart is required to install an update. Windows displays a notice before the restart, and the device should be on and connected.

Needless to say, only enable this feature if you really believe this is actually the correct approach, as such a behavior may become annoying for Windows users and even result in losing unsaved work.

If this feature is enabled, users around the Windows 10 device will see a notification covering the entire screen and requiring a method reboot:

It’s almost time to restart
You’ve chosen to restart your device as quickly as possible when an update is pending, and one is ready for you now.
We’ll restart to install this update at /time/ or you can restart sooner. Remember to leave our device switched on and plugged in.

Exactly the same screen at the path above includes a choice to show notifications when a reboot is required, so perhaps this is a easier system for users inside an organization:
Show a notification when your PC needs a restart to finish updating

After making changes in this screen, there’s no need to reboot your device, as all settings are saved automatically.

However, IT admins attempting to manage updates better could turn to different ways of doing this instead of enable these reboots on Windows 10.

The option to restart the device ASAP when it is necessary to install an update was implemented in Windows 10 version 1903, or Windows 10 May 2019 Update, so it’s not available in the previous OS versions.

For instance, there isn’t any such option in Windows 10 October 2018 Update (version 1809) and older.

Latest Windows 10 update has a bug that kills VPN connection

Microsoft has confirmed the Windows 10 May 2019 Update (version 1903) contains a bug that could break the Remote Access Connection Manager (RASMAN) service on some devices, consequently killing users VPN connections.

In an update to its support document, the company says the bug has effects on Windows 10 version 1903 using the KB4497935 update installed.

According to Microsoft’s updated changelog, the RASMAN service may cease working and administrators or users will get an “0xc0000005” error whenever a system running the latest form of Windows 10 is manually configured to the non-default telemetry setting of zero.

The issue itself is the place a VPN profile is configured being an Always on VPN (AOVPN) without or with device tunnel. Luckily though, the problem does not affect manual-only VPN profiles or connections which are more widely used by consumers looking to secure their devices online and prevent unwanted tracking.
RASMAN issues

If you do make use of an Always on VPN connection though, you can fix the problem by setting a new value for two group policy settings:

Group Policy Path: Computer Configuration\Administrative Templates\Windows Components\Data Collection and Preview Builds\Allow Telemetry
Safe Policy Setting: Enabled and set to 1 (Basic) or 2 (Enhanced) or 3 (Full)

Alternatively, you may make the following changes to the Registry:

SubKey: HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Microsoft\Windows\DataCollection
Setting: AllowTelemetry
Value: 1, 2 or 3

After applying these changes to either the group policy settings or registry, you will have to restart the Remote Access Connection Manager service to allow them to work.

Windows 10 is really a step closer to never needing passwords

Microsoft’s vision of a passwordless future is one step closer to being a reality now that the organization has gained official FIDO2 certification for Windows 10‘s biometric authentication system, Windows Hello.

The certification is perfect for the Windows 10 May 2019 Update (Windows 10 version 1903) that is scheduled to be made publicly available at the end of May.

Currently Windows 10 users may use Windows Hello to access their devices using a fingerprint or by facial recognition on their PC.

Users can now sign in to Microsoft accounts with no password
World Password Day: is that this the last one?
Empowering CISOs to bolster password security

In a article announcing the Windows Hello Fido2 certification, group manager for Microsoft’s crypto, identity and authentication team in Azure Core OS, Yogesh Mehta explained the business’s reasoning behind trying to eliminate passwords, saying:

“People don’t like passwords because we have to remember them. As a result, we often create passwords that are simple to guess-which makes them the very first target for hackers trying to access your pc or network at work.”

FIDO2 certification

Since Windows Hello has gained FIDO2 certification, users can expect to determine FIDO Certified logos on new Windows 10 PCS.

The Windows 10 1903 FIDO2 certification will also extend beyond Microsoft’s software and users will be able to log to their Microsoft Account and also to other FIDO-supported sites from Mozilla Firefox. Windows Hello authentication may also be visiting the business’s Chromium-based Edge browser soon.

Based on Microsoft, users will be able to register using Windows Hello to the various apps and services including Outlook, Office 365, Skype, OneDrive, Cortana, Xbox Live on PC, the Microsoft Store and more.

The times of utilizing a traditional password are slowly coming to an end and thankfully Microsoft and other tech giants for example Google are fully embracing our passwordless future.

Microsoft Confirms Surface dGPU Bug in Windows 10 May 2019 Update

Microsoft has recently discovered an insect in Windows 10 May 2019 Update affecting the Surface Book 2 equipped with Nvidia’s discrete graphics processing unit, also known as dGPU.

The software giant states that after installing this latest Windows 10 feature update, the graphics compatibility bug could cause some games or apps to crash on the Surface Book 2.

“Microsoft has identified a compatibility issue on some Surface Book 2 devices configured with Nvidia discrete graphics processing unit (dGPU). After updating to Window 10 version 1903 (May 2019 Feature Update), some apps or games that needs to perform graphics intensive operations may close or neglect to open,” the organization explains.

Surface Book 2 blocked from install version 1903

As a result, Microsoft will quickly set a new upgrade block on the Surface Book 2 using the said hardware, so these units would not be offered the upgrade to Windows 10 May 2019 Update.

“To safeguard your update experience, we have applied a compatibility hang on Surface Book 2 devices with Nvidia dGPUs from on offer Windows 10, version 1903, until this issue is resolved,” Microsoft says.

Surface Book 2 units which have recently been upgraded to Windows 10 version 1903 and therefore are hitting this issue can turn to an extremely simple temporary workaround. Microsoft recommends users to reboot their devices or to head over to Device Manager and scan for hardware changes.

However, this only fixes the problem for any limited time. Microsoft does not recommend Surface Book 2 owners to manually update their devices to Windows 10 May 2019 Update while using Media Creation Tool or any other method.

Meanwhile, a fix has already been within the works, also it ought to be published within an upcoming release. An ETA hasn’t been provided just yet through the software giant.

Windows 10 Version 1903 Adoption Barely Improves But This Isn’t Not so good news whatsoever

New figures provided by AdDuplex reveal that the adoption of Windows 10 May 2019 Update, or version 1903, improves in a really slow pace, but while some could be tempted to believe this is another failed release, this is unlikely to become the case.

AdDuplex data implies that Windows 10 April 2018 Update (Windows 10 version 1803) happens to be the leading Windows 10 version available on the market having a share of 58%, accompanied by Windows 10 October 2018 Update (Windows 10 version 1809) with 30%.

Windows 10 May 2019 Update (Windows 10 version 1903) is just third with 6.3%.

“Windows 10 May 2019 Update (1903) has gained around 5% since last month and is now on 6.3% of near to 100,000 PCs surveyed. This puts it on par with the pace of 1809 30 days after its re-release. Which is, probably, a bad sign as we have seen how this ended (just over 30% install base before the next release went),” the AdDuplex report reads.

Cautious rollout of Windows 10 May 2019 Update

As the adoption from the new feature update seems to match the main one from the version 1809, the reasons behind the slow migration to the May 2019 Update is probably different from what these figures appear to suggest.

Most users chose to delay the upgrade to Windows 10 October 2018 Update due to the bugs in the update. Microsoft even pulled the update completely after it discovered a glitch which could have caused the complete elimination of some user files kept in libraries.

But in the situation from the May update, the slow adoption may be the consequence of Microsoft releasing the brand new version to only a number of devices, because it wants to make sure that widespread issues are discovered before they hit a more significant quantity of devices.

The update is pushed in stages to devices via Windows Update, and seekers can get it with a manual check for updates in Windows 10.