- Windows 10’s May Update Occurs an Error that can be a painful experience
- Microsoft has already rushed an emergency
- Be sure to apply that FIX before installing the May Update – but if you have already encountered this error there is still a way out
Windows 10 users need to be aware of a fresh error in the latest update to us, although it is a mistake that will be much more widespread with Business -Bearing computers rather than consumer machines.
That’s because your Windows 10 PC encounter the problem, it can be quite ugly to have to save your system from – and you can avoid any potentially technically traumatic episode by simply installing an emergency FIX Microsoft has just rushed out.
Windows latest reported the problem of the May update to Windows 10, causing a affected PC to fail to install the upgrade and then run an automatic repair – a process that can happen several times, confusing.
To add additional confusion is that if you have Bitlocker or Device Encryption turned on (so the data on your drive is encrypted), you end up on the recovery screen. This recovery process asks for your central ID and if you do not have the info to give then you are in something of a pickle, we must say.
However, let’s cover these important warnings first, but the most important thing is that to be affected, your PC must run an Intel VPRO processor (10th gene or newer). This is because the error relates to Intel Trusted Execution Technology (TXT for short), which is part of the VPRO array of security measures.
As the name suggests, VPRO is a brand of chips that are mostly used for professional (business) notebooks, but they are also found in consumer -carrying computers. As Microsoft notes: “Consumer units typically do not use Intel VPRO processors and are less likely to be affected by this problem.”
It is worth checking if your PC has such an Intel VPRO chip inside and if it has, if you haven’t already installed the May update for Windows 10 22H2, no matter what you do, push the break on it.
Instead of grabbing the cumulative May update to avoid that error, be sure to install Microsoft’s emergency top that was deployed yesterday.
This is KB5061768, which you can only install manually – it will not be provided by Windows Update. Get it from Microsoft’s update catalog here and download the variant ‘Windows 10 Version 1903 and later’, which is correct for your PC. (It is probably the 64-bit (or x64) version checks your process type in the unit device specifications in System> About In the Settings app, but if you do not have a 64-bit CPU and us, you will have the X86 version, ignore the arm variant).
Breaks down the problem – and what to do if you are already hit and locked out of your PC
What actually happens to this error? There is some problem with the May update to Windows 10 that causes a process (LSASS.EXE, a security -related service) to be completed unexpectedly. This causes the automatic repair process to run to try to solve things, but as mentioned above, your Windows 10 -PC may make more repeated failed attempts to install the update before giving up and rolling back to the previous (April) update (hopefully).
It’s messy, but things are worse for those who use device encryption or bitlocker, which may end up getting stuck on the recovery screen if they don’t have their recovery key to hand.
So what happens if you have missed the boat to install this emergency from Microsoft, since you have already installed the May update for Windows 10 and now you can’t get into your system (past the recovery screen) to download and apply that fix?
In this case, Microsoft advises that to start Windows 10 successfully, you must turn off the Intel Trusted Execution Technology and another setting, Intel VT to Direct I/O, in your PC’s BIOS. However, it seems to require entering your Bitlocker recovery key (again, problematic if you do not have it available).
If you are stuck in this particular dead end, according to Windows, it is latest possible to simply turn off the Intel Trusted Execution Technology (TXT) in your BIOS without touching the second setting (Intel VT) and then you can successfully restart your PC to get back to desktop.
The first step here is to enter the BIOS and the method of doing this varies depending on your PC (check the manuals delivered with your machine). The key to accessing BIOS can be one of a number of options, but it is often F2, F10 or F12 that you press repeatedly as the system just starts to boot.
When in BIOS, find the Intel TXT option (or trusted execution technology). This is probably in security> virtualization or system security settings or some label relating to security or system configuration. It is likely to be a security -related title, so check carefully through such option screens looking for Intel TXT. When you find this, turn it off, but as mentioned you can leave Intel VT to direct I/O alone.
Now select the option to save changes to BIOS and restart your PC and you must be back in Windows 10, where you can now install Microsoft’s Patch (KB5061768) from the Update Catalog. Once done, you can go back to your BIOS and switch the Intel TXT back on.
All in mind, to avoid potential messy like this, it is a much better idea to install the correction before grabbing the cumulative update to Windows 10.
This is not the first time Microsoft has visited an error like this on Windows 10 users (or actually Windows 11 PCS). It is also worth remembering that if you run Windows 11 and you upgrade to the latest version, 24h2, using a clean installation, this device’s encryption feature will automatically use. Note that an on -site upgrade to Windows 11 24h2 will not do this, only a clean installation of Windows 11 24h2. In addition, it must also be an installation linked to a Microsoft account, as this is where encryption recovery key info is stored (which is why you need to be very careful to delete a Microsoft account as the key disappears with it).
Device encryption is basically a ‘Lite’ version of Bitlocker that delivers encryption to Windows 11 at home -PCs, but it only covers the data on the main system driven.
