Oem62.inf
Jon Levatte
Malfunctioning hardware, missing, corrupt, or deleted oem62.inf device drivers can result in these Norton 360-related errors. If your INF file is suffering from one of those troubles, replacing it with a fresh file should resolve the issue.
These types of errors will normally stop occuring if the correct oem62.inf file version is placed in the right location, but you should double-check that is the case. To confim it's resolved, try starting up Norton 360 to see if the error can be triggered.
The majority of oem62.inf BSOD errors happen after fresh install of new hardware or software (Norton 360). Mostly, oem62.inf-related errors are experienced during the Norton 360 install process, while a Symantec-related software or hardware is loaded, during a Norton 360-related device driver load sequence, or Windows shutdown/startup. It's important to notate when Blue Screen errors with oem62.inf happen, as it helps troubleshoot Norton 360-related problems, and report them back to Symantec.
An incorrect device driver was released for Windows 10, on March 8, 2017, that affected a small group of users with connected phones or portable devices. After installation, these devices are not detected properly by Windows 10, but are affected in no other way.
Of course, it's the best choice to use system restore to roll back a faulty update. This will work in Windows 7 and Windows 8.1 (hopefully). Windows 10 users are facing probably trouble. While system restore shall work in Windows 10 RTM and Windows 10 Version 1511, Windows 10 Version 1607 users run into the issue I've addressed within my blog post Windows 10 Version 1607: System restore error 0x80070091 [Fix].
Well, because it's a driver update, this update can't be uninstalled via Windows Update. The only solution is a driver rollback. So the 2nd approach to fix the issue, proposed from Microsoft, is a rollback of the MTP driver. This is described within my blog post Windows 10 Version 1607: System restore error 0x80070091 [Fix].
Microsoft has pulled the faulty update from Windows Update servers, after we reported the issues with mobile devices. So this package should no more been offered to Windows systems via Windows Update.
But, if the update has been installed, the faulty drivers are in driver cache. Each attempt in updating the MTP driver will result in a broken mobile device detection. Microsoft describes now, how to clean the driver cache from the faulty package.
1. Open an administrative command prompt window (type cmd in search box of Windows 7, 8.1 or 10, right click the result and select context menu command Run as administrator, see also Windows 10: Open command prompt window as administrator).
It should be something like oem##.inf with a one or two digit number after the oem in the name, and have the Driver date and version as shown in the above example. Then enter the following command and press enter:
where the ## is the number in the file name noted above (for instance oem62.inf). The command removes the faulty driver package from driver cache. When you disconnect and reconnect your device, it should not reinstall the incorrect driver.