Tools & Consulting for the webMethods® platform

Tools & Consulting for the webMethods® platform

Fixing Windows 10 update problem with WinRE partition

There are (as of May 2024) update issues on many Windows 10 systems due to a bug in Bit Locker. If you get error "0x80070643" and updates are not installed, you need to fix this manually.

If you are “lucky” like me, you have recently seen update failures on Windows 10 systems , showing the error 0x80070643 .

The underlying reason in my case (and probably for you as well) is a security issue with BitLocker and Microsoft has been working on a fix for a while. In some cases the chosen approach seems to conflict with the size of partition of the Windows Recovery Environment. Microsoft has now finally surrendered (Windows release health notes entry), in that you will need to adjust the partition size by yourself. At least they provide a PowerShell script, which you can find here.

This page will not be kept up-to-date, so please verify with Microsoft that this still applies. The steps below have worked on multiple machines as of May 3, 2024.

The following steps are a log of what I have done on several notebooks here. While everything has worked well for me, these actions can potentially destroy your Windows 10 installation. If this is not your personal machine, you should absolutely check with your administrator/helpdesk.

If you follow the instructions, you do this at your own risk !

Here is what I have done

  • Reboot machine to ensure that no update activites are still open
  • Create directory to store the script and a sub-directory for the backup of Windows RE:

        md c:\temp\winre_part\backup

  • Open your editor of choice and safe the PowerShell script (link here) into c:\temp\winre_part\enlarge.ps1
  • Open PowerShell as Administrator and change into c:\temp\winre_part
  • Check whether you are allowed to run the PowerShell script by running this command. Remember the response (you will likely get Restricted):


  • Allow execution of script by typing:

      Set-ExecutionPolicy bypass

  • Run the script by typing enlarge.ps1 and specify c:\temp\winre_part\backup as backup directory
  • Change execution policy back to its original setting:
  • Reboot your machine
  • Check for updates and install fixes

Update: You may have to re-enbale WinRE

On one machine (the only one with a German localization) the script failed to re-enable the Windows Recovery Environment (WinRE). In consequence the security update also failed. This was solved by manually re-enabling WinRE.

I used the Administrator-level PowerShell that was still open and ran “reagentc /enable“. After that the update was successful.



Leave a Reply

Your email address will not be published. Required fields are marked *

On Key

Related Posts

Running webMethods Integration Server in containers

Organizations are moving from traditional deployments to containers and Kubernetes to increase business agility. This article discusses a lot of topics that are relevant to actually reach the goal of faster delivery of value to the business through software. Because if you do it wrong, you just end up with yet another technology stack. And, as always, technology is not your biggest challenge.

Legacy software: Better than its reputation

Moving away from “legacy software” is easier said than done. It is a complex combination of business and technical aspects that needs to be looked at.

Having worked on a number of migration projects over the last 20 years, here are my thoughts. It is just a “short” overview but will give you a starting point for things to look at.

Update connection details for JDBC adapter on webMethods Integration Server

Connections to a an external database are mostly environment specific. So they must be adjusted whenever a new instance of Integration Server gets deployed. In some situations that can be done manually, in others automation is mandatory. The tool described here can do this for you and is ideal for use in a container scenario.

Performance tuning for webMethods Integration Server

Having spent a lot of time with performance tuning on webMethods Integration Server, I wanted to share some thoughts here. They will equip you with a starting point and the flexibility to go wherever your project takes you.