April Updates Cause 0x800f0203 Error: How To Fix It OK, now that you know how many updates were supposed to be installed, let’s talk about preventing the BSOD, so that you can get all of your updates installed. To do so, you’ll need a little bit of computer knowledge and the willingness to edit some files. If you have those qualities, you can probably resolve the problem(s) and get the updates installed correctly within a few minutes. If you don’t feel comfortable tracking down and altering a few text files, you might want to simply alter your Windows Update settings to prevent the updates from trying to install for a while. Microsoft will undoubtedly issue an updated package (no pun) to resolve the problems causing the BSODs, as soon as possible. Follow these steps to fix the BSOD issues: Login with admin rights. Backup your data (just in Case). Open the setupapi.dev.log logfile. It will be located in the c:\windows\inf folder. Find the error “Failed to install device instance” from your latest retry. The entries are time stamped. Above this error it will say which file caused the problem. The file will always have a .INF extension. As an example, let’s say it’s the “oem90.inf” that is causing the problem (in addition, it seems to be the most common file causing the issues). Run “pnputil -d <Problem File Name>” from an elevated command prompt. In this example, it would be “pnputil -d oem90.inf” (no quotes). Manually re-run windows update and the update should run correctly. If it does not, repeat this process because it’s possible that you have multiple files within the updates that need “fixing” in the driver store. That said, if you have to fix more than 3 files, you might be better off resetting your Surface as there is probably a bigger problem at play. In the interest of credit where credit is due, this reddit thread is where I first learned about the 0x800f0203 BSOD problem and the potential fix for it.