[German]Windows users – and especially users of Windows 10 and Microsoft Surface devices – are affected from time to time by the boot error 0xc0000098. I will therefore prepare the whole thing again in a blog post

I had already addressed this error in the German blog for Windows 8. But yesterday I had a call for help from a doctor from Japan, who ran into this error with a Surface Pro 6 and was left helpless (not the best in the days of Corona virus). So I decided to sum some thing up, to help affected victims.

The error

Windows 10 (and of course also the older Windows 8.1) is facing some users – mostly after an update installation – an error 0xc0000098 at boot time and the system can’t boot anymore. This results in a so-called BlueScreen, which displays the error message “Windows Boot Configuration Data does not contain valid OS Entry”. 

The message indicates that Windows did not find a valid entry on the boot configuration of the operating system at startup. This information can be found in the path \Boot\BCD in the BCD store. What is the cause, how can this be solved?

The cause is usually an unsuccessful update where the BCD entries on the boot files are overwritten incorrectly. This can happen on normal Windows 10 systems, but it is also more common on Microsoft’s Surface Tablet PCs.

Repair the error in the BCD store

I will take up a Microsoft Answers forum post about this error on a Surface Go from  November 2019. MVP colleague Barb Bowman describes the repair approach you can try.

1. As soon as the Surface hits the BlueScreen, the device should be switched off via the start button.

2. Repeat this procedure three times to force the automatic repair in Windows RE. 

Then you should see a page with a blue background where you can click or tap the Advanced Options button. Then you should see the Choose an option page from Windows PE.

Select the Troubleshooting tile to go to the next page with the Advance options shown below.

Select the tile Command Prompt to open the command prompt window of Windows PE. Then try to enter the commands given below to repair the BCD data base:

bootrec /scanos
bootrec /rebuildbcd
bootrec /fixmbr
bootrec /fixboot

The commands are is not case-sensitive, only there must be a space between bootrec and the / character. Each of the lines must be terminated with the Enter key. When all commands have been completed successfully, you can close the command prompt window, and let Windows 10 start new ones. With any luck, the BCD entries are repaired, and the system will boot again.

The ‘Restore System’ option can also be seen in the above dialog box. You can try if a restore point exists and the system can be restored to a working state via this point. Unfortunately, Microsoft has been turning off System Restore on every Windows 10 feature update for some time now, so the approach is usually not usable.

In this blog post, a victim describes another approach to repair the Surface Go with a recovery drive. 

Reset the Surface, if the BCD repair doesn’t work

If the above approaches do not work, you can try to reset the Surface to the factory settings with a ‘fresh’ Windows 10. But this will deletes all files and programs that you have installed.

Tip: If you are able to boot into Windows PE, you can try to back up the user files to a USB device using the Windows editor Notepad. The Open dialog box can be used as a mini file manager (see the following figure). Set the file filter to *.*. Then you can use the dialog box do select files, copy it to clipboard, move to a drive and copy the files using the insert clipboard command. Only the refresh won’t work properly. As an alternative you can use the command prompt to copy or move files.

Microsoft has published this support article describing how to reset the Surface to factory settings. Some hints can also be found in this forum post (deleted). I can’t assist further with details regarding Surfaces (because I never bought such an overpriced and buggy device). But maybe the steps above are helpful.

[German]Sometimes Windows 10 users run into errors during update installation. And the Windows troubleshooter then reports errors in the Windows Update database that can’t be fixed. Usually this ends up in a new installation or an in-place upgrade of Windows 10. Are there potential errors in the Windows Update database that could cause this issues? In two parts the problem is analyzed – and it is shown how to probably get around a new installation or an in-place upgrade by a repair.

German blog reader Andi O. had already pointed out the observation to me some time ago and sent me a compressed text about the facts of the case. I will just compiled it into an article I release here. At this point my thanks to Andi for the extensive tests – and sorry that it took a few days to prepare the text.

Error in Windows Update database

Blog reader Andi already had issues with Windows Update at Windows 10 version 1803. When running the Windows Update troubleshooter, it was always reported that there were potential errors in the Windows Update database. It was recommended that Windows Update should be repaired.

Unsuccessful attempt to repair

If something like this happens, the user naturally tries to carry out such a repair. Andi writes that he tried everything he found on the Internet in this case.

• This started with batch instructions, which can be downloaded under #6 from A. Reilland in this German forum.
• Also two tools au_check_v78f and winUpdRestore!v28 were tested without success. Both tools where provided in ancient days by German MS Answers forum moderators, who developed the solution many years ago, but later got fired, because Microsoft found cheaper supporters going eastward. The download if these tools is possible under #13 on German site Dr. Windows.

But according to Andi in his feedback, nothing helped. The only approach that helped him was an in-place upgrade repair. To do this, one simply reinstalls Windows in a running Windows, which results in a reinstallation of all Windows system files, without losing data and programs or apps.

Researched again

Sometime later a feature upgrade to Windows 10 version 1903 arrived. Andi wrote, that he had already put the above research to rest and, according to his own statement, would not have bothered with them anymore. But then he came across this post while researching Windows 10 Help. There, my MVP colleague André da Costa describes five ways to fix Windows Update problems and repair Windows Update. The in-place upgrade that helped with Andi is also included. Andi asked himself whether this was one of the possibilities for the solution he was looking for?

A new investigation and new tests

To answer the above question, he had to go back to Windows 10 version 1803 and test. So he did a downgrade to this Windows 10 build. This can also be done via in-place upgrade by installing an image of Windows 10 version 1803 under the running Windows 10 version 1903.

The only difference is that when you ask what you want to keep, you have to answer the lowest point “Nothing. Everything will be deleted, e.g. files, apps and settings”.

Of course, this means that data and apps/programs as well as settings on the system drive will be lost. Since Andi only had Windows installed anyway, but no applications, this was no problem. He also had a backup available in case of an emergency.

At this point some comments from Andi and from me. After reinstalling Windows 10 version 1803 Andi used used wushowhide to disable the feature upgrade to version 1909. That worked so far.

Andy  actually wanted to take the most recent one of 1803 as an example. But Windows Update decided to use the 17134.1345. The he tried the Windows Update catalog. With the download of the KB’s for the feature update, there was no problem. But the installation failed. Although he chooses the 64 bit version, both KB’s , KB4540689 (17134.1365) and KB4541333 (17134.1399) , gave an error message: “The update is not suitable for your computer.” Therefore you have to be content with 17134.1345.

Windows Update again has errors

Immediately after downgrade, Andi checked the Windows update database in Windows 10 version 1803 for potential errors. Andi assumed that the errors in the Windows Update database could be caused by an incorrect installation of updates.

• • To do this, he navigated to Programs and Features in the Control Panel and then to the Show Installed Updates section.

Then he uninstalled the individual Updates and used Windows Update to have the updates reinstalled again and performed the troubleshooting.

The conclusion of this approach: He wasn’t successful to found something. No errors were reported from the Windows Update database.

New idea: Are drivers to blame?

Then it occurred to him that it might be related to updated Windows drivers, although he had no idea what drivers should have to do with the update database.

• So in a further step, he uninstalled the third-party drivers one by one.
• Immediately after uninstalling a driver, he let em re-installing via Windows Update (without rebooting in between these steps).

After each step, troubleshooting was performed to identify any errors in Windows Update. Andi writes: ‘I was lucky. Errors were displayed this time’. After clicking on Show detailed information, the following diagnostic information was suddenly displayed.

All screenshots here a kept in German, but I guess, it needs not too much phantasy to map it to other languages.

The above dialog box reports an error, but does not provide an indication of the exact cause. Instead it lists fixed errors and an unfixed issue in the Windows Update database. Since he uninstalled and then installed individual drivers, he knew which driver was involved. The cause was this time the Intel Bluetooth 20.60.0.4 driver.

Traces in the Event Viewer

herefore he called the Windows Event Viewer. This can be done, depending on the Windows version, in the search field of the Start menu or the task bar, via the entry ‘Event’ and the hit event viewer. The following entry was found in the Event Viewer:

The update error 0x8024CE16 was reported. Andi writes that he executed the troubleshooter several times. During each run, the troubleshooter reported that errors have been fixed, but that wasn’t the case. The conclusion is that nothing was fixed at all.

Do the old troubleshooting tips help?

So, after Andi was able to provoke the bug in the update database, he next worked through the five tips from André da Costa linked above. All these tips proved to be unhelpful, except for the radical method ‘Windows repair as in-place upgrade’, which has been mentioned already several times in the above text.

Andi then took another look at the Event Viewer. He noticed an inconsistency in the Bluetooth driver mentioned above. In the Event Viewer there was the error message from the above picture. According to Andi, Windows Device Manager reports everything was fine in contradiction.

Since he is not using Bluetooth, he cannot confirm the message that everything is okay. But if this were the case and Bluetooth was working properly, Andi would close, then the message in the event display would be a misdiagnosis.

A suspicion: incorrect diagnosis in the update database

At this point, the suspicion arose that the Events might be involved and that the troubleshooter might not be able to handle that. So it would be something like a classic false diagnosis. This suspicion will be investigated in part 2.

Article series:
Potential errors in the Windows update database – Part 1
Potential errors in the Windows update database – Part 2

Similar articles
How to decode Windows errors?
Windows 10: Analyze upgrade errors
Windows: How to decode update 0x8024…. errors
Check and repair Windows system files and component store
Windows Update Error 0x80246001
Windows Update Error 0x8007042B
Windows Update error 0x8024200D

[German]In Part 1 I had taken up a reader’s note that after Windows fails to install updates, there are potential errors in the Windows Update database which can’t be repaired by Update trouble shooter. In part 2 I describe further diagnosis steps, a root cause for the issues and a repair approach.

From Part 1 there was the suspicion that a driver install issues may be involved the Windows Update database error reported by the troubleshooter. The suspicion is: Does the troubleshooter report something wrong because the error is in the event logs?

Is the troubleshooter reporting something false?

For Andi, the findings from part 1 were followed by the question: “Is it conceivable that the troubleshooter reports “potential errors in the update database” as a false diagnosis and instead the text “potential errors in the event viewer” should be displayed?

Therefore he decided to selectively delete the event logs. This is not a problem, since the log could be saved before the events were deleted. And if any errors that occurs are logged as events again. Once the error is gone, no new entry is written in the event display, of course.

The Event Viewer display is structured hierarchically. The entries relevant for the following test are located in the Windows Logs branch (see figure above). The entries are divided into various categories.

The entries can be deleted in the Windows Logs branch of the Event Viewer running with administrative rights via the context menu or in the Action/Delete menu.

#1 Delete events under Application

In the first step, Andi deleted the entries in the Windows Logs\Application branch of the Event Viewer. Then the troubleshooter was executed. The result was the message: “potential errors in the Windows Update database”, which was actually to be expected.

#2 Delete events under Security

In the next step, the entries in the Windows Logs\Security branch of the Event Viewer were deleted. Afterwards, the troubleshooter was performed, which returned the message: “potential errors in the Windows Update database”. This was also to be expected, since errors in the update database should not have anything to do with security events.

#3  Delete events under Installation

There is another branch called Installation in the Event Viewer. This should be a ‘hot candidate’ for a test, as it’s where problems that occur during the installation of components in Windows are entered. So in a further step in the Event Viewer, delete the entries in the Windows Logs\Installation branch.

Then the Windows Update troubleshooter was launched to analyze the data base for errors. And Bingo, there was a change! The troubleshooter suddenly reported: “The problem could not be identified by the troubleshooter” (see figure below).

Note: In the following text, Andi suggests deleting the entries in the System branch instead of the Installation branch. My recommendation here would be to successively delete the individual branches under Windows Logs, if necessary.

Verifying the process again

After these steps Andi decided to run all tests again to document this. In the German screenshots below, he shows the date and time in the background (taken from as time service).

Start with no Windows Update database error

The test was started in a state that the troubleshooter does not report an error in the Windows Update database.

So first, Andi checked what the troubleshooter determines about the state of the update database. This ended with the result shown in the figure above. The troubleshooter reported: “The problem could not be identified by the troubleshooter”.

Uninstalling and reinstalling drivers

Then Andi uninstalled the Intel Wireless Bluetooth driver in Device Manager (see the following figure).

He then had Windows Update check for updates. During this step a driver should be found and installed.

A driver was found (see figure above) and he had it installed. Then it was checked whether the Bluetooth driver was installed.

Check the update database for errors

Exciting question: What does the troubleshooter will report after installing the Bluetooth driver initiated by Windows Update?

The troubleshooter reports again and as expected, an error in the Windows Update database.

‘’Repair’ the update database via the Event Viewer

So the next step is to repair the Windows Update database by ‘Delete the event logs’. To do this, you can access the event viewer by either searching the taskbar or right-clicking on the Windows logo in the left corner of the taskbar, followed by a left-click on “Event Viewer”.

Then double-click on the Windows Logs branch in the left column. Right-click on System to open the context menu and choose the context menu command Delete Log… is selected. Confirm the deletion in the dialog box shown.

Andi wrote: The cmd window unfortunately disappeared after clicking on the event viewer. Therefore no proof of the Windows version is possible here. And he deleted here entries in System instead of Installation. It’s mandatory to try, which Event viewer branch need to be deleted to fix the database error.

Repair of the Windows Update database was successful after this step, as the troubleshooting diagnosis for Windows Update shows afterwards.

This proved that the diagnosis of the Windows Update troubleshooter reported false results and can’t fix broken things.

Conclusion of the whole action

Anyone running into issues with Windows Update on Windows 10 and is using the Windows Update troubleshooter, must remain vigilant. If the troubleshooter reports errors in the Windows Update database that can’t be fixed, they might be the result of corresponding entries in the event logs.

Anyone who gets into this situation should try to clear the logs in the Event Viewer under Windows Update. The procedure has been described above in detail – and this clearing has no consequences for Windows functionality (only entries that could be used for troubleshooting are gone – and this can be prevented by saving the entries before deleting them).

Andi was successful with approach in Windows 10 version 1803. This approach should help with “potential errors in the Windows update database” even with newer versions of Windows 10. At this point my thanks to Andi for the extensive testing and preparation, so that I could publish this in this blog post.

Article series:
Potential errors in the Windows update database – Part 1
Potential errors in the Windows update database – Part 2

Similar articles
How to decode Windows errors?
Windows 10: Analyze upgrade errors
Windows: How to decode update 0x8024…. errors
Check and repair Windows system files and component store
Windows Update Error 0x80246001
Windows Update Error 0x8007042B
Windows Update error 0x8024200D

On April 8, 2020, Microsoft released the Windows 10 Insider Preview Build 19603 (20H2 development branch) for Insiders in the Fast Ring. In the Windows Blog, Microsoft lists the new features, bug fixes and known problems of this build. For example, there is an integration of the Windows Subsystem for Linux (WSL) in Windows Explorer.

[German]Microsoft has released the update KB4552455 for Windows 10 V2004 in the slow ring of the Insider program on April 9, 2020. This is the Windows 10 version that is planned to be released in spring 2020 (currently rumored to be a May update).

The announcement was made on the Windows-Blog  by Brandon LeBlanc. The build number will increase to 19041.173. The update contains the same fixes as for Build 19041.172. Additionally the following fixes have been rolled out:

• Microsoft fixed an issue that prevents older versions of certain apps from opening by directing users to install the latest version of these apps.
• Microsoft have fixed an issue that fails to allocate resources during device initialization, which causes certain USB mass storage devices to stop working.
• Microsoft have fixed an issue that prevents the mute button from working on certain devices with the Your Phone app.
• Microsoft have fixed an issue that causes a fault in the input-output memory management unit (IOMMU) and a DRIVER_VERIFIER_DMA_VIOLATION (e6) error. This issue occurs after resuming from hibernate on systems that have Kernel Direct Memory Access (DMA) Protection and Dynamic Root of Trust Measurement (DRTM) enabled.
• Microsoft have updated the Country and Operator Settings Asset (COSA) to increase the coverage for automatic cellular provisioning on devices with mobile broadband.

This update has a known issue: Narrator and NVDA users who use the latest version of Microsoft Chromium Edge may experience some difficulty navigating and reading certain Web content. Narrator, NVDA, and the Edge teams are aware of these issues. Users of older versions of Microsoft Edge are not affected. NVAccess has released NVDA 2019.3 that solves the known Edge issue.

[German]The optional update KB4541335 released by Microsoft at the end of March 2020 for the Windows 10 versions 1903 and 1909 causes nasty issues for some users. These range from installation errors to to blue screens.

The update KB4541335 for Windows 10 V190x

The optional update KB4541335  dated March 24, 2020 is cumulative and raises the OS build to 18362.752 (Windows 10 V1903) or 18363.752 (Windows 10 V1909). The update is available for Windows 10 version 1903, for Windows 10 version 1909, and for Windows Server version 1903 and Windows Server version 1909. It contains quality improvements but no new operating system features.

Various installation errors

I had listed the list of changes in the blog post Windows 10 190x: Update KB4541335. Microsoft does not report any known issues with this update. In the above blog post I already pointed out that some users cannot install the update. The installation stops with Error 0x800f0831 (ERROR_SXS_ASSEMBLY_MISSING), 0x800f0922, 0x800f0986 (see e.g. here, here, here), 0x80070003 (Path Not Found, see also here), 0x80070490 (see also here) or general problem messages or causes other errors (see e.g. here). In the linked articles at the end of the article I partly deal with these installation errors.

Temporary user profile

The well-known bug that is already present in the latest updates (see Windows 10: Update KB4532693 kills user data/profile) also affects some users of update KB4541335 (see this MS Answers forum post with meanwhile 3 pages of user messages). After installing the update, a temporary user profile is loaded during user login. The only thing that helps here is to uninstall the update and wait for the next patchday.

BlueSceen Page Error in Nonpaged Area and Connection Manager

In this Microsoft Answers forum post, a user reports a BlueScreen Page Error in Nonpaged Area. After uninstalling the update, this error is gone. In this specific case it is traced back to ArcSoft files. .

In this MS Answers forum post t a user complains about flickering of the screen and spontaneous restarts (probably after BlueScreen). He states the Windows Connection Manager as the cause.

Boot and performance problem after update installation

In this MS Answers forum post a user ran into the issue after installing the update, that his notebook becomes slow. Antivirus and firewall were disabled and the HP Support Assistant issued a warning. The user removed and suspended the update.

This user is complaining about high CPU load and related performance issues related to the update. Here the display language of the desktop has changed after installing the update.

And this user reports, that after installing the KB4541335 update, the message ‘No Operating system could be found’ appears. The boot files are gone and the machine can no longer boot.

These are all single messages that will have different causes. However, it is unpleasant for the affected persons one way or another.

Fix for Freezes

Bodgan Popa from Softpedia describes in this article a workaround for an annoying problem he had. All applications caused the operating system to freeze when calling the Open or Save As dialog boxes. Most of the time, people fix it by killing the Explorer process in the Task Manager. The behavior seems to be related to the search settings. Bodgan Popa then disabled the options in Explorer to display recently used files and frequently used folders, and the problem was gone.

Similar articles:
Windows 10 190x: Update KB4541335
Windows 10 V1903: Update install error 0x80073701 confirmed
Windows Server 2016: Feature-Installation Fehler 0x80073701
Win 7 SP1-Fehler 0x80073701 (Assembly Missing)
Windows: Patchday Issues March 2020?
Windows 10: Update error 0x800F0922
Windows 10 Update drops error 0x80070490

Windows 10: Update KB4532693 kills user data/profile
Windows 8.1: Update KB4537821 kills also user profiles
Windows 8.1/10: What’s the status of the user profile bug?
Windows Server 2012/R2/Terminal server: Temporay user profiles after February 2020 Updates

How to decode Windows errors?
Windows 10: Analyze upgrade errors
Windows: How to decode update 0x8024…. errors
Check and repair Windows system files and component store

[German]German blog-reader Martin Feuerstein has pointed out a curious issue with app installing in Windows. When trying to install an app in Windows 10, he got the error message ‘The app you’re trying to install isn’t a verified app from the Store’. Here is some information about this issue.

Martin writes that on Windows 10 he received a warning when he tried to download and install an app (in his case it was Spotify). But Martin is not alone – while writing this post I came across this Microsoft Answers forum post with a similar problem (there is was TurboTax 2019).

Warning after App download

The situation, Martin suddenly faced: He downloaded the Spotify exe installer from spotify.com. Then he installed the app und got later on one system the warning ‘The app you’re trying to install isn’t a verified app from the Store’ every time a user logged on and tried to launch the program. The screenshot shown below is from this Microsoft Answers forum post.

The application could not be installed. The whole thing is crude, of course, since it is an official Spotify app. Martin included some information about the environment in his mail.

• The PC is newly installed with Windows 10 1809, no S-mode. The PC is installed just like the other computers and also in the domain, the ‘gp-Pack PaT against the biggest telemetry messes’ is implemented according to Martin and also the Windows Store has been deactivated. So a system for business use. 
• Only the necessary drivers (Lenovo H530s) are installed. Standard software like Firefox, Foxit Reader, 7-Zip, Open-Shell and VLC media player are installed on the client. The same programs are also installed on other domain computers. However, the programs work there without any warning message.

Martin wrote me: When I first installed the computer, Spotify was downloaded and installed with the Microsoft Edge (without warning). Afterwards Spotify was moved from Appdata to a directory directly in c:\, so that another user account can also call the program.

That’s when the problems started. As soon as Spotify has been started for the first time from the respective user account, the above message appears at every Windows logon. This is true even if Spotify is not in autostart or has even been deleted from the hard disk. You can get grey hairs there.

Blame the Internet zone flag?

Martin did some research and writes about it: “We believe the problem is related to the Internet zone flag or zone identifier on a executable”. This flag is set when files are downloaded from the Internet. The state of this flag can be set in the properties of an executable file on the General tab via the Security/Allow option. Below is the German version of the property box – a similar description in English may be found here.

Because Martin was able to bypass the problem in the second attempt by deleting the Internet zone flag in question. However, as Martin wrote, the whole thing was a ‘long journey’ until it worked.

• First, he reset the Internet flag in the Intel graphics driver’s auxiliary programs started in the user context. But that did not bring any improvement.
• Then he checked the installed EXE files in the program directory and reset their Internet flag. But the error persisted.
• After a new installation of Windows 10 on the computer, the installation program of Spotify – this time downloaded with Firefox – was immediately blocked with the above message.
• Afterwards Martin removed the Internet flag from the installation program. Then the program was installed and moved to another directory.

When he checked the program files, the Internet flag was no longer set. The program started afterwards without the error message shown above. It is an old experience that you should reset the Internet zone bit on downloaded files before installation to avoid issues.

Martin writes: ‘I probably didn’t reset the Internet flag of the installer on the first attempt (although the files themselves are downloaded and written to disk by the installer)’. Finally Martin Feuerstein has a little PowerShell tip to reset the Internet flag of several files, e.g. for newly downloaded drivers:

Get-ChildItem –Recurse –Path <Hier Pfad einsetzen> | Unbloc

At this point I would like to thank Martin Feuerstein for his feedback. Maybe it will help someone who is affected.

Note: There is this MS Answers forum post, suggesting to got to the Settings app, navigate to ‘Apps & features’ and choose the App install option ‘Anywhere’. But I guess, that won’t help, because the Apps mentioned above are not from the store. By the was, I found mentions since spring 2020 – so it could be a but.

[German]On April 14, 2020 (second Tuesday of the month, Patchday at Microsoft) several cumulative updates for the supported Windows 10 builds were released. Here are some details about the respective updates.

A list of the updates can be found on this Microsoft website. I have extracted the details below. The update installation requires an existing current Servicing Stack Updates (SSUs). Meanwhile, Microsoft publishes an overview of current Servicing Stack Updates (SSUs) under ADV990001 (if it is not up to date, have the Microsoft Update Catalog search for Servicing Stack Updates).

Updates for Windows 10 Version 190x

Microsoft provides the same update packages for the Windows 10 builds 1903 and 1909 that were released in 2019. The following updates are available for the Windows 10 May 2019 Update (version 1903) and the Windows 10 November 2019 Update (version 1909).

Update KB4549951 for Windows 10 Version 190x

Cumulative Update KB4549951 raises  the OS build to 18362.778 (Windows 10 V1903) or 18363.778 (Windows 10 V1909). The update is available for Windows 10 version 1903, for Windows 10 version 1909, and for Windows Server version 1903 and Windows Server version 1909. It contains quality improvements but no new operating system features. Here is the list of enhancements, referred to by Microsoft as highlights:

• Updates to improve security when using Microsoft Office products.
• Updates to improve security when Windows performs basic operations.
• Updates for storing and managing files.

The update adds the following fixes and improvements to Windows 10 version 1909, which are identical to version 1903 (update is also available for the Hololens)

• Addresses an issue that prevents certain apps from installing if they are published using a Group Policy Object.
• Addresses an issue that prevents a wired network interface from obtaining a new Dynamic Host Configuration Protocol (DHCP) IP address on new subnets and virtual LANs (VLAN) after wired 802.1x re-authentication. The issue occurs if you use VLANs that are based on accounts and a VLAN change occurs after a user signs in.
• Security updates to the Microsoft Scripting Engine, Windows App Platform and Frameworks, Windows Cloud Infrastructure, Windows Virtualization, Microsoft Graphics Component, Windows Kernel, Windows Media, Windows Shell, Windows Management, Windows Fundamentals, Windows Virtualization, Windows Storage and Filesystems, Windows Update Stack, and the Microsoft JET Database Engine .

This update is automatically downloaded and installed by Windows Update. This update is also available in the Microsoft Update Catalog and via WSUS. Microsoft strongly recommends that you install the latest service stack update (SSU) for your operating system before you install the latest cumulative update (LCU). For this update, Microsoft indicates that there is no known issue.

Microsoft has also released an update directly for the Windows Update Client to improve its reliability. This is rolled out outside of Windows Update if the machine is compatible and not an LTSC variant and updates have not been blocked by GPO.

Servicing Stack Update KB4552152

On March 10, Microsoft also released the SSU KB44552152 for Windows 10 version 1903 and 1909. Microsoft says:

This update makes quality improvements to the servicing stack, which is the component that installs Windows updates. Servicing stack updates (SSU) makes sure that you have a robust and reliable servicing stack so that your devices can receive and install Microsoft updates.

The SSU should have been installed before installing any other cumulative updates.

Updates for Windows 10 Version 1809

The following updates are available for Windows 10 October 2018 Update (version 1809) and Windows Server 2019.

Update KB4549949 for Windows 10 Version 1809

Cumulative Update KB4549949 the OS build (according to MS) to 17763.1158 and includes quality improvements but no new operating system features. Here is the list of improvements, called highlights by Microsoft:

• Updates to improve security when Windows performs basic operations.
• Updates to improve security when using Microsoft Office products.
• Updates for storing and managing files.

Added are the following fixes and improvements to the Windows version:

• Addresses an issue that prevents certain apps from installing if they are published using a Group Policy Object.
• Security updates to the Microsoft Scripting Engine, Windows Kernel, Windows App Platform and Frameworks, Microsoft Graphics Component, Windows Media, Windows Shell, Windows Management, Windows Cloud Infrastructure, Windows Fundamentals, Windows Virtualization, Windows Core Networking, Windows Storage and Filesystems, Windows Update Stack, and the Microsoft JET Database Engine.

This update is automatically downloaded and installed by Windows Update. This update is also available in the Microsoft Update Catalog. Microsoft strongly recommends that you install the latest service stack update (SSU) for your operating system before you install the latest cumulative update (LCU). Microsoft lists a known issue that this update causes. For details, see the KB article.

Microsoft has also released an update directly to the Windows Update client to improve its reliability. This is rolled out outside of Windows Update if the machine is compatible and is not an LTSC variant and updates have not been blocked by GPO.

Servicing Stack Update KB4549947

On March 14, Microsoft also released the SSU KB4549947  for Windows 10 version 1809. Microsoft writes that it brings improvements to the servicing stack to make the update installation more reliable. SSU should be installed before installing any further cumulative updates.

Updates for Windows 10 Version 1507 bis 1803

For Windows 10 RTM up to version 1803, various updates are available for the LTSC versions and, if necessary, the Enterprise versions. The Home and Pro versions on the other hand have been dropped from support. Here is a short overview.

• Windows 10 Version 1803: Update KB4550922 is only available for Enterprise and Education. The update raises the OS build to 17134.1425. The fixes mentioned in the KB article are included. This update is automatically downloaded and installed by Windows Update, but is available for download from the Microsoft Update Catalog. Before manual installation, the latest Servicing Stack Update (SSU) must be installed. Details, including known issues, can be found in the KB article.
• Windows 10 Version 1709: Update KB4550927 is only available for Enterprise and Education. The update raises the OS build to 16299.1806. The fixes mentioned in the KB article are included. This update is automatically downloaded and installed by Windows Update, but is available for download from the Microsoft Update Catalog. Vor Before manual installation, the latest Servicing Stack Update (SSU) must be installed. Details, including known issues, can be found in the KB article.
• Windows 10 Version 1703: Update KB4550939 is only available for the Surface Hub. The update raises the OS build to 16299.2346. The fixes mentioned in the KB article are included.
• Windows 10 Version 1607: Update KB4550929 is now available only to Enterprise LTSC. The update raises the OS build to 14393.3630. The fixes mentioned in the KB article are included. This update is automatically downloaded and installed by Windows Update, but is available for download from the Microsoft Update Catalog. Before manual installation, the latest Servicing Stack Update (SSU) must be installed. Details, including known issues, can be found in the KB article.
• Windows 10 Version 1507: Update KB4550930 is available for the RTM version (LTSC). The update raises the OS build to 10240.18545. The fixes mentioned in the KB article are included. This update is automatically downloaded and installed by Windows Update, but is available for download in the Microsoft Update Catalog. Before manual installation, the latest Servicing Stack Update (SSU) must be installed. Details, including known issues, can be found in the KB article. Details can be found in the KB article.

There was no update for Windows 10 V1511 and V1703, because these versions were dropped from support. Details about the above updates can be found in the respective Microsoft KB articles in case of doubt.

Similar articles:
Microsoft Office Patchday (April 7, 2020)
Microsoft Security Update Summary (April 14, 2020)
Patchday: Windows 10 Updates (April 14, 2020)

On April 15, 2020, Microsoft released the Windows 10 Insider Preview Build 19608 (20H2 development branch) for Insiders in the Fast Ring. In the Windows Blog, Microsoft lists the new features, bug fixes, and known issues of this build. There is an optimized assignment of apps in the settings page.

[German]Microsoft has released the update KB4550936 for Windows 10 V2004 in the slow ring of the Insider program on April 14, 2020. This is the Windows 10 version that is planned to be released in spring 2020.

The announcement was made in the Windows-Blog by Brandon LeBlanc. The update increases the build number to 19041.207. The update contains the following quality improvements and fixes:

• We fixed an issue that causes the Remote Procedure Call (RPC) service (rpcss.exe) to close unexpectedly and the device stops working. Then you must restart the device.
• We fixed an issue that causes the Device Enrollment Status Page (ESP) on managed devices to stop responding if a policy that requires a restart is installed on the device.
• We fixed an issue that might prevent the rear camera flash from functioning as expected on devices that have a rear camera.
• It also includes the latest security updates to the Microsoft Scripting Engine, Windows Kernel, Windows App Platform and Frameworks, Microsoft Graphics Component, Windows Media, Windows Shell, Windows Management, Windows Cloud Infrastructure, Windows Fundamentals, Windows Authentication, Windows Virtualization, Windows Core Networking, Windows Storage and Filesystems, Windows Update Stack, and the Microsoft JET Database Engine.

This update has a known issue: Narrator and NVDA users who use the latest version of Microsoft Chromium Edge may experience some difficulty navigating and reading certain Web content. Narrator, NVDA, and the Edge teams are aware of these issues. Users of older versions of Microsoft Edge are not affected. NVAccess has released NVDA 2019.3 that solves the known Edge issue.

As of April 17, 2020, Microsoft has released update KB4557426 for Insider in the Fast Ring for the Windows 10 Insider Preview Build 19608 (20H2 development branch). The addendum to the post on the Windows Blog states that the build will increase to 19608.1006. The update contains an unspecified improvement to increase stability.

[German]In all versions of Windows, there is a vulnerability in the Microsoft Graphics component that could allow an attacker to escalate privileges. Details are now available.

The Windows Graphics Vulnerability CVE-2020-0791

Microsoft has already released details of the Windows graphics vulnerability CVE-2020-0791 on March 10, 2020. A vulnerability exists in the Windows graphics component that allows privilege escalation because objects in memory are not processed properly. An attacker who successfully exploited this vulnerability could run processes with elevated privileges.

In a local attack scenario, an attacker could exploit this vulnerability by running a specially crafted application to take control of the affected system. Microsoft states on its CVE-2020-0791 website that the vulnerability is unlikely to be exploitable. On this page the exploitability score is given as 3.9. Furthermore, the vulnerability was not publicly known at the time. However, Microsoft has released security updates to close this vulnerability in March 2020. The updates and Microsoft’s classification can be found at Microsoft’s website at CVE-2020-0791. 

CheckPoint Research reveals details

For people who deal with vulnerabilities: CheckPoint Research has just released details of the Windows graphics vulnerability CVE-2020-0791. The following tweet refers to this release.

[CPR-Zero] CVE-2020-0791 (Windows 10 Kernel): Out-Of-Bounds Read\Write in the StrechBlt function in win32kfull.syshttps://t.co/PGg9X2bNHE

— Check Point Research (@_CPResearch_) April 20, 2020

The vulnerability is found in the module win32kfull.sys and occurs in the StrechBlt function. This allows an out-of-bounds read/write operation. The security researchers have published a Proof of Concept (PoC) for Windows 10 version 1909, which crashes this Windows with a blue screen.

[German]On April 21, 2020, Microsoft released a monthly preview rollup for Windows 8.1 as well as optional updates for various Windows 10 versions. Here is an overview about these optional updates.

Updates for Windows 10

These are so-called C-Week-Updates, which are released as optional updates in the third week of a month. A list of the updates can be found on this Microsoft website. I have pulled out the details below. The update installation requires an existing current Servicing Stack Updates (SSUs). Microsoft now publishes an overview of current Servicing Stack Updates (SSUs) under ADV990001 (if it is not up to date, have the Microsoft Update Catalog search for Servicing Stack Updates).

Update KB4550945 for Windows 10 Version 1903/1909

Cumulative Update KB4550945 raises the OS build to 18362.815 (Windows 10 Version 1903) and 18363.815 (Windows 10 Version 1909). It contains improvements and bug fixes but no new operating system features. The following is listed as highlights:

• Updates an issue that prevents certain apps from opening after you upgrade from a previous version of Windows, and a Bad Image error message appears. 
• Updates in an issue that turns off notifications for devices that use a virtual private network (VPN) on a cellular network. 
• Updates an issue that prevents you from resuming a Microsoft Xbox game on a Windows device after upgrading from a previous version of Windows. 
• Updates an issue that causes a text box that contains multiple lines of text to stop responding in certain scenarios. 
• Updates an issue that generates unexpected notifications when you change the default application settings. 
• Updates an issue that causes Windows Update to stop responding when you check for updates. 
• Updates an issue that fails to print content that is outside of the margins of a document.

Here is the list of improvements brought by this update:

• Addresses an issue that prevents certain apps from opening after you upgrade from a previous version of Windows, and a Bad Image exception dialog box appears. 
• Addresses in an issue that turns off notifications for devices that use a virtual private network (VPN) on a cellular network. 
• Addresses an issue that prevents you from resuming a Microsoft Xbox game on a Windows device after upgrading from a previous version of Windows. 
• Addresses an issue that causes a box that contains multiple lines of text to stop responding in certain scenarios. 
• Addresses an issue that prevents the touch keyboard from appearing during sign in when the user is prompted for the password. 
• Addresses an issue that prevents the touch keyboard from opening in Universal Windows Platform (UWP) apps when USB devices are connected. 
• Addresses an issue that displays incorrect folder properties in File Explorer when the path is longer than MAX_PATH. 
• Addresses an issue that prevents the correct lock screen from appearing when all of the following are true:
  • The Group Policy Object (GPO) policy “Computer Configuration\Windows Settings\Security Settings\Local Policies\Security Options\Interactive Logon: Do not require Ctrl+Alt+Del Computer” is disabled.
  • The GPO policy “Computer Configuration\Administrative Templates\System\Logon\Turn off app notifications on the lock screen” is enabled.
  • The registry key HKLM\SOFTWARE\Policies\Microsoft\Windows\System\
    DisableLogonBackgroundImage is set to 1.
• Addresses an issue that generates unexpected notifications related to changing the default application settings.

• Addresses an issue that causes the sign in screen to be blurry. 
• Addresses an issue that causes Windows Update to stop responding when you check for updates. 
• Addresses an issue that prevents the Sign in options page from opening using the ms–settings:signinoptions-launchfingerprintenrollment Uniform Resource Identifier (URI). 
• Addresses an issue with Bluetooth group policy settings on Microsoft Surface Pro X devices. 
• Addresses an issue that causes a KERNEL_SECURITY_CHECK_FAILURE (139) stop error when Windows resumes from Sleep and turns on certain Bluetooth headsets. 
• Addresses a reliability issue in WDF01000.sys. 
• Addresses an issue that causes an error in logman.exe. The error is, “A user account is required in order to commit the current Data collector Set properties.” 
• Addresses an issue that prevents users from setting the REG_EXPAND_SZ keys in some automated scenarios. 
• Addresses an issue that causes a memory leak in the LsaIso.exe process when the server is under a heavy authentication load and Credential Guard is enabled. 
• Addresses an issue that causes the Trusted Platform Module (TPM) initialization to fail with system event error 14 and prevents Windows from accessing the TPM. 
• Addresses an issue that causes communication with the TPM to time out and fail. 
• Addresses an issue that prevents hash signing using the Microsoft Platform Crypto Provider for TPMs from working correctly. This issue might also affect networking software, such as VPN applications. 
• Addresses an issue that prevents applications running in an Azure Active Directory environment from receiving account change notifications. This occurs when using the Web Account Manager (WAM) and the WebAccountMonitor API. 
• Addresses an issue that causes systems to stop working with a 0x3B stop code when running a binary that is signed by a revoked certificate. 
• Addresses an issue with merging Windows Defender Application Control policies that sometimes generates a duplicate rule ID error and causes the Merge-CIPolicy PowerShell command to fail. 
• Addresses an issue that prevents a user’s PIN from being changed after connecting the device to Microsoft Workplace Join. 
• Addresses an issue that fails to print content that is outside of the margins of a document.
• Addresses an issue that prevents Microsoft Internet Information Services (IIS) management tools, such as IIS Manager, from managing an ASP.NET application that has configured SameSite cookie settings in web.config.
• Addresses an issue that causes Microsoft Edge to stop working if you attempt to use paste functionality on webpages when cut-and-paste functionality has been disabled using a policy and Windows Defender Application Guard is active.
• Addresses an issue that causes the Clipboard service to unexpectedly stop working.
• Addresses an issue that displays a black screen to Windows Virtual Desktop users when they attempt to sign in.

This update is optional and does not need to be installed. To get it you have to download and install it (after a search if necessary) in the Windows Update settings page. This update is also available in the Microsoft Update Catalog and via WSUS. Microsoft strongly recommends that you install the latest service stack update (SSU) for your operating system if you install the latest optional cumulative update (LCU). Microsoft is not aware of any issues with this update. 

Microsoft has also released an update directly to the Windows Update client to improve its reliability. This is rolled out outside of Windows Update if the machine is compatible and is not an LTSC variant and updates have not been blocked by GPO.

Update KB4550969 for Windows 10 Version 1809

Cumulative Update KB4550969 raises the OS build to 17763.1192. t contains improvements and bug fixes but no new operating system features. The following is given as highlights:

• Updates an issue with pasting mixed content of images and text from Microsoft Word into Internet Explorer. 
• Updates an issue that causes a text box that contains multiple lines of text to stop responding in certain scenarios. 
• Updates an issue that fails to print content that is outside of the margins of a document.

Here is the list of improvements that this update brings

• Addresses an issue that occurs when a third-party application loads hidden tabs into Internet Options. 
• Addresses an issue with pasting mixed content of images and text from Microsoft Word into Internet Explorer. 
• Addresses an issue that causes a box that contains multiple lines of text to stop responding in certain scenarios. 
• Addresses an issue that prevents the first key stroke from being recognized correctly in the DataGridView cell. 
• Addresses an issue that causes an application that uses msctf.dll to stop working, and the 0xc0000005 (Access violation) exception appears. 
• Addresses an issue that prevents the correct lock screen from appearing when all of the following are true:
• The Group Policy Object (GPO) policy “Computer Configuration\Windows Settings\Security Settings\Local Policies\Security Options\Interactive Logon: Do not require Ctrl+Alt+Del Computer” is disabled.
• The GPO policy “Computer Configuration\Administrative Templates\System\Logon\Turn off app notifications on the lock screen” is enabled.
• The registry key HKLM\SOFTWARE\Policies\Microsoft\Windows\System\
  DisableLogonBackgroundImage is set to 1.
• Addresses a reliability issue in WDF01000.sys. 
• Addresses an issue that causes a KERNEL_SECURITY_CHECK_FAILURE (139) stop error when Windows resumes from Sleep and turns on certain Bluetooth headsets. 
• Addresses an issue that causes the Event Viewer Microsoft Management Console (MMC) to stop working when the secondary monitor is above the primary monitor. An out of bounds exception appears. 
• Addresses an issue that causes an error in logman.exe. The error is, “A user account is required in order to commit the current Data collector Set properties.” 
• Addresses an issue that prevents users from setting the REG_EXPAND_SZ keys in some automated scenarios. 
• Addresses an issue that causes a memory leak in the LsaIso.exe process when the server is under a heavy authentication load and Credential Guard is enabled. 
• Addresses an issue that prevents hash signing using the Microsoft Platform Crypto Provider for TPMs from working correctly. This issue might also affect networking software, such as VPN applications. 
• Addresses an issue with merging Windows Defender Application Control policies that sometimes generates a duplicate rule ID error and causes the Merge-CIPolicy PowerShell command to fail. 
• Addresses an issue that prevents a user’s PIN from being changed after connecting the device to Microsoft Workplace Join. 
• Addresses an issue that prevents applications running in an Azure Active Directory environment from receiving account change notifications. This occurs when using the Web Account Manager (WAM) and the WebAccountMonitor API. 
• Addresses an issue that fails to print content that is outside of the margins of a document. 
• Addresses an issue that prevents Microsoft Internet Information Services (IIS) management tools, such as IIS Manager, from managing an ASP.NET application that has configured SameSite cookie settings in web.config. 
• Addresses an issue that causes high CPU usage on Active Directory (AD) domain controllers when migrating to Windows Server 2019. This increases latency in Microsoft Exchange operations, causes Managed Store contention, and severely impacts index creation in Active Directory and the Global Catalog’s performance. 
• Addresses an issue that logs incorrect Internet Protocol (IP) addresses in the audit logs because of missing or old data for active requests coming from “windowstransport/usernamemixed/certificatemixed” endpoints. 
• Addresses an issue that causes devices that are provisioned for Windows Hello for Business (WHfB) to fail. Registration occasionally fails, which leads to a delay in WHfB enrollment and, in some instances, creates Conflicting Objects (CNF) in the Active Directory “Registered Device” container. 
• Addresses an issue that might cause a deadlock in the Remote Desktop Gateway service. 
• Addresses an issue that might cause the Remote Desktop Gateway service to stop working. 
• Addresses an issue that causes systems to stop working with a 0x3B stop code when running a binary that is signed by a revoked certificate.
• Addresses an issue that prevents the Notification State registries from being deleted for certain apps even after the user profile is deleted.
• Addresses an issue that causes stop error 0x18 (REFERENCE_BY_POINTER) when Remote Desktop sessions redirect devices that are not input devices.
• Addresses an issue that displays a black screen to Windows Virtual Desktop users when they attempt to sign in.

This update is optional and does not need to be installed. To obtain it, you must download and install it (possibly after a search) from the Windows Update settings page. This update is also available in the Microsoft Update Catalog and through WSUS. Microsoft strongly recommends that you install the latest service stack update (SSU) for your operating system before you install the latest cumulative update (LCU). Microsoft lists a known issue. If update KB4493509 is installed on a machine, installing the update may cause the error code:

0x800f0982 = PSFX_E_MATCHING_COMPONENT_NOT_FOUND

when certain Asian language packs are installed. In this case, all subsequently installed Language Packs must be uninstalled and the cumulative update KB4493509 installed. Details can be found in the KB article.

Microsoft has also released an update directly for the Windows Update Client to improve its reliability. This is rolled out outside of Windows Update if the machine is compatible and not an LTSC variant and updates have not been blocked by GPO.

Updates for Windows 10 Version 1507 till 1803

For Windows 10 RTM up to version 1803, various updates are available for the LTSC versions and, if necessary, the Enterprise versions. The Home and Pro versions on the other hand have been dropped from support. Here is a short overview.

• Windows 10 Version 1803: Update KB4550944 is only available for Enterprise and Education. The update raises the OS build to 17134.1456. The fixes mentioned in the KB article are included. This update is automatically downloaded and installed by Windows Update, but is available for download from the Microsoft Update Catalog. Before manual installation, the latest Servicing Stack Update (SSU) must be installed. Details, including known issues, can be found in the KB article.
• Windows 10 Version 1607: Update KB4550947 is only available for Enterprise LTSC. The update raises the OS build to 14393.3659. The fixes mentioned in the KB article are included. This update is automatically downloaded and installed by Windows Update, but is available for download from the Microsoft Update Catalog. Before manual installation, the latest Servicing Stack Update (SSU) must be installed. Details, including known issues, can be found in the KB article.

There was no update for other Windows 10 versions. If in doubt, details about the above updates can be found in the respective Microsoft KB articles.

Updates for Windows 8.1/Windows Server 2012 R2

A Preview Monthly Rollup has been released for Windows 8.1 and Windows Server 2012 R2. The update history for Windows 8.1 can be found on this Microsoft page. 

KB4550958 (Monthly Rollup) for Windows 8.1/Server 2012 R2

Update KB4550958 (Preview of Monthly Rollup for Windows 8.1 and Windows Server 2012 R2)contains improvements and fixes from the latest updates and a preview of the following month’s updates. The preview update addresses the following issues.

• Addresses an issue that prevents Microsoft Internet Information Services (IIS) management tools, such as IIS Manager, from managing an ASP.NET application that has configured SameSite cookie settings in web.config. 
• Addresses an issue that might cause certain operations, such as rename, to fail when you perform those operations on files or folders that are on a Cluster Shared Volume (CSV). The error is, “STATUS_BAD_IMPERSONATION_LEVEL (0xC00000A5)”. This issue occurs when you perform the operation on a CSV owner node from a process that doesn’t have administrator privilege.
• Addresses an issue that prevents certain apps from installing if they are published using a Group Policy Object.

This update is offered and installed via Windows Update, but is also available in the Microsoft Update Catalog and via WSUS. In case of a manual installation, the latest Servicing Stack Update (SSU KB4540725) must be installed before. According to Microsoft there should be no problems with the update – but I would not install it, because it is a preview update.

Similar articles:
Microsoft Office Patchday (April 7, 2020)
Microsoft Security Update Summary (April 14, 2020)
Patchday: Windows 10 Updates (April 14, 2020)

[English]On April 22, 2020, Microsoft released the Windows 10 Insider Preview Build 19613.1000 (20H2 development branch) for insiders in the Fast Ring. Microsoft describes in the Windows Blog the new features, bug fixes and known issues of this build.

[German]As of April 22, 2020, Microsoft has released a cumulative update (KB4558244) for the Windows 10 version 2004 for insiders in the slow ring. This update raises the build to 19041.208. It fixes an issue that prevents NPLogonNotify API notifications from being sent from the Credential Provider Framework. The announcement was published in the Windows Blog.

[German]On patchday, January 14, 2020, Microsoft has closed the vulnerability CVE-2020-0624 (Win32k Elevation of Privilege) with security updates. Now I have found a Proof of Concept (PoC).

Vulnerability CVE-2020-0624

In Windows, an Elevation of Privilege vulnerability CVE-2020-0624 exists in the Win32k file. The vulnerability is privilege escalation because the Win32k component does not handle objects in memory correctly.

An attacker who successfully exploited this vulnerability could execute arbitrary code in kernel mode. This would allow the attacker to install programs, view, modify, or delete data, and create new accounts with full user privileges.

However, to exploit this vulnerability, an attacker would have to log on to the system first. An attacker could then run a specially crafted application that could exploit the vulnerability and take control of an affected system.

Affected systems

The following Windows systems are affected by the vulnerability, which Microsoft considers unlikely to be exploited:

• Windows 10 Version 1903
• Windows 10 Version 1909
• Windows Server Version 1903 (Core)

Microsoft has released security update KB4528760 on January 14, 2020 to close the vulnerability (see Patchday Windows 10-Updates (January 14, 2020)). However, update KB4528760 caused several problems (see links at the end of this article).

Proof of Concept for CVE-2020-0624

The following tweet brought me across a use-after-free proof of concept (PoC) for CVE-2020-0624 by James William.

Windows 10 win32k EoP vulnerability proof-of-concept code.
CVE-2020-0624https://t.co/nq8bEMdX10

— James Willy (@james0x40) April 22, 2020

The code may be fount at GitHub.

Similar articles:
Patchday Windows 10-Updates (January 14, 2020)
Windows 10: Issues with Update KB4528760 / KB4532695
Windows 10: Installation issues with Update KB4528760 due to missing Connect-App?Windows 10 V1909: Update KB4528760 drops error 0x800F081F

[German]Short advance notice for next May (19 and 20 May 2020). At this time the Microsoft //Build 2020 conference (virtual) will take place. Microsoft also wants to stream two webcasts for Windows Insider in the mixer channel.

This is stated in the following tweet. There will be two webcasts on two days.

#WindowsInsider webcast announcement! We’ll be hosting two webcasts in May for #MicrosoftBuild2020!

Dates, times, and a link to our @WatchMixer channel are posted in the Answers forum! Check the link below for all the details:https://t.co/VsPLU4lrDY pic.twitter.com/rOV80zUvqE

— Windows Insider (@windowsinsider) April 28, 2020

The details can be found in the Microsoft Answers Forum for Windows Insider in this thread.

• Session 1: Tuesday, May 19 – 2 to 4 AM GMT  (7pm-9pm PDT)
• Session 2: Wednesday, May 20 – 5 to 7 PM GMT  (10am-12pm PDT)

But these are somewhat unchristian times: 2 to 4 o’clock GMT. I don’t know if anybody intends here in Europe to go online within the night, to follow a webcast (the last time I did this was the video sessions streamed on broadcasting stations during moon landing, back in 1969 and in the 70ties).

[German]On April 29, 2020, Microsoft released the Windows 10 Insider Preview Build 19619.1000 (20H2 development branch) for insiders in the Fast Ring. In the Windows Blog Microsoft lists the new features, bug fixes and known problems of this build.

[German]Microsoft released version 0.17 of PowerToys for Windows 10 users a few hours ago. These tools are free and offer nice additional features for Windows 10. The new version 0.17 includes the code for an auto-update for the tools, but it can be tested with upcoming v0.18.

PowerToys Background

PowerToys were free programs under Windows 95/98, with which certain Windows features could be optimized or adapted. Inspired by the PowerToys project under Windows 95, some developers dared to restart. The intended was to give power users the ability to get more efficiency out of the Windows 10 shell and customize it for individual workflows. The announcement tool place at the beginning of May 2019 (Windows 10: PowerToys will come as Open Source). More information can be found in the articles linked at the end of this blog.Windows 10: Erste Open Source PowerToys freigegeben.

(PowerToys Settings)

The PowerToys known from Windows 9x are also available in the version for Windows 10 Open Source and free of charge.

Update to Windows PowerToys 0.17

The announcement was made on April 30, 2020 by developer Clint Rutkas – here his corresponding tweet with the message.

Why hello #powerToys 0.17 into the world. Some great improvements. https://t.co/N37lS8e6Mw

— Clint Rutkas (@ClintRutkas) April 29, 2020

The details including the release notes can be found on this GitHub page. Version 0.17 is an update that was designed to improve stability and upgradeability. The biggest new feature is the auto-update function, which has now been implemented. But this feature can’t be tested until an update (probably v0.18) is available.

Rutka mentioned also that ha has added telemetry built into the new PowerToys 0.17 version. This should help to prioritize the FancyZone developments. Rutkas writes that it was known that there was a subset of bugs. In order to see how many users were affected, telemetry was used, which then made it possible to do the work faster than planned. A list of the fixes can be found here – an extract of the fixes:

• PowerToys can now update itself #1686
• FancyZone can now snap to two zones (still experimental since it doesn’t support restoring the app to two zones)
• Per machine installation fixed, non-admin user will be able again to use PowerToys after the regression in 0.16.
• Fixed most of the FancyZones Virtual Desktop bugs.
• Fixed several FancyZones bugs including proper handling of taskbar position.
• PowerToys icon in the Start menu will always show

Details and the download are also available on this GitHub page.

Similar articles:
Windows 10: First Open Source PowerToys released
PowerToys v0.12 Beta released
PowerToys v0.13 released
PowerToys 0.14.0 released
PowerToys 0.14.1 released
Windows 10: PowerToys get QuickLauncher
PowerToys 0.15.0 released
Windows 10: PowerToys Version 0.16 released
Windows PowerToys 0.16.1 released

[German]As of April 30, 2020, Microsoft has released the Windows 10 Insider Preview Build 19041.208 as a new RTM in the Release Preview Ring. This is the 20H1 development branch, which will soon be released as Windows 10 May 2020 Update (Version 2004).

An addendum in the Windows Blog states that build 19041.207 was originally planned as RTM, but now build 19041.208 is used as RTM candidate. Build 19041.208 is rolled out by KB4558244, is cumulative and contains all 20H1 features as well as all fixes published for Windows Insiders in the slow ring in Build 19041.21 to Build 19041.207.

Also fixed is an issue where NPLogonNotify API notifications cannot be sent by the credential provider framework. Note that the May 2020 update is initially only automatically rolled out to a subset of Windows insiders in the Release Preview Preview ring.

All other users in the Windows Insider program who have opted for the Release Preview Ring can manually go to Settings > Update & Security > Windows Update. There you can manually check for updates and then decide to install the offered May 2020 update. Please also note that the new build still has known problems:

• Windows Mixed Reality may not work correctly for many users with the May 2020 update. For those who use Windows Mixed Reality regularly, Microsoft recommends that you do not use the preview of the Windows 10 May 2020 update for the time being. Microsoft is working on a fix that we hope to release in early May.
• Microsoft is aware of an issue where using the Deployment Image Servicing and Management (DISM) tool to repair damage on systems that are running the May 2020 update may not always display the correct status. This will be corrected in a future service release.
• Some applications use the ImeMode property to control the IME (Input Method Editor) mode for individual text input fields to increase input efficiency. This functionality is currently not working correctly in the May 2020 update. For example, a number field does not automatically switch to a mode that is best optimized for Japanese numeric input. This issue will be resolved in a future service update.

To work around this latter problem of the IME mode property for a short time, either switch the input mode manually while typing or select the ‘Use previous version’ compatibility checkbox for the affected keyboard via Settings > Time & Language.