On July 12, Microsoft confirmed that there is a bug in the Windows 11 June optional update (KB5039302). This bug affects the Windows Update Agent API and causes issues for users and devs. After users install this update, they face problems with PowerShell or VBScript scripts that call the API. These scripts return empty results when trying to get some object properties, which leads to the error code 0x8002802B “TYPE_E_ELEMENTNOTFOUND.” This bug impacts users of the Windows 11 22H2 and 23H2 updates, while Windows Server systems are not affected.
The main impact of this bug is on users who need scripts to manage updates. The error can slow down work and cause stress. Many users, from single users to large firms, face this issue due to the bug’s presence in both update versions.
Microsoft’s Response
Microsoft has noted the bug and is working to limit its effect. The firm is using the Known Issue Rollback feature to fix the problem. This tool helps lessen the damage without making users take extra steps. Still, in some cases, IT teams must use special group rules to fully solve the issue.
The Known Issue Rollback tool lets Microsoft turn off the bad update. This means users do not have to take action, which helps keep their systems running well.
For some cases, IT staff may need to take more steps to fix the issue. Microsoft gives tips on how to set up special group rules to manage the bug’s effect on systems and ensure updates work as they should.
Additional Bugs in KB5039302 Update
The KB5039302 update has brought other issues too. Users have said that the update makes virtual machines restart over and over and causes the taskbar to fail to load. These issues add to the stress for users who depend on their systems for work.
Gizchina News of the week
One big issue from the KB5039302 update is the loop of restarts for virtual machines. This bug stops normal use, making it hard for users to finish their tasks. This is a big deal for firms that rely on virtual machines for key work.
Another key problem is the taskbar loading fail. Users have said the taskbar does not load after the update, which harms how they use the system and makes it tough to access key tools and features.
To solve these issues, users and IT teams must take steps. For the loop of restarts in virtual machines, users may need to roll back the update or find other ways to fix the bug. For the taskbar loading fail, a system restart or reinstalling the update may help clear the problem.
Conclusion
The KB5039302 update for Windows 11 has caused several bugs that harm users and IT teams. Microsoft has seen these issues and is working to limit their effects. The Known Issue Rollback tool and special group rules help deal with the main bug tied to the Windows Update Agent API. Still, extra steps may be needed to fix other bugs like the restart loop for virtual machines and the taskbar loading fail.
Though updates are key for keeping system safety and speed, they can bring new issues at times. Users must stay aware of possible issues and take steps to limit their impact. Microsoft’s steps in response to the KB5039302 update bugs show its aim to fix user concerns and keep the user experience smooth. By using tools like the Known Issue Rollback and giving tips to IT teams, Microsoft aims to cut the stress caused by these bugs and help users keep their systems working well.What do you think about Microsoft’s effort so far, is it enough? Let us know your thoughts in the comment section below