This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(128, 8%, 22%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EA%3C/text%3E%3C/svg%3E)
***UPDATE, I DID NOTHING AND TONIGHT MY COMPUTER NO LONGER SHOWS THESE ERRORS. MICROSOFT MUST HAVE FIXED IT***
Please help me to resolve this matter.
The troubleshooting steps I see listed do not work with an updated current Surface Laptop 4.
Locked Question. This question was migrated from the Microsoft Support Community. You can vote on whether it's helpful, but you can't add comments or replies or follow the question.
Thank you to everyone for reporting this problem and providing feedback.
I am pleased to report that the Windows Update team at Microsoft was able to resolve this problem on 2/16/2023, at around 10:30am PST.
If you are still experiencing this problem, please report your issue to our engineering team via the Feedback Hub.
This answer has been deleted due to a violation of our Code of Conduct. The answer was manually reported or identified through automated detection before action was taken. Please refer to our Code of Conduct for more information.
Comments have been turned off. Learn more
Sort of relieved that I'm not the only one getting this "install error" with a bunch of drivers.
Is anyone else's touchpad reeeeally sluggish? Like it takes a whole quarter-second to register any touches. Any short strokes just completely don't register at all because of this. I have a Lenovo ThinkPad X13s which runs on ARM. I have to resort to the little trackpoint just because of this.
thank you, this worked for me, surface pro 7 w/ windows 11
I paused updates for one week. Immediately checked for updates. There was an update from MS. Downloaded and installed the update and it seems to have solved the problem. Have no idea why this works, knocking on wood that the fix holds. Thanks to those who posed this solution.
Do you know what the update was named? It should be in the history of installed updates or, failing that, check the reliability report.
