Note the name of the oemXX.inf file that it is coupled with. Open %temp%\oem_drivers.txt in your handy dandy text editor and search for prnms006.inf.Run pnputil /enum-devices >%temp%\drivers.txt.Run pnputil /enum-drivers >%temp%\oem_drivers.txt.This is to prevent office from kicking off the install again in the future and making a NEW oemXXX.inf. ![]() Go to C:\Program Files\Microsoft Office\root\Office16 and rename OneNote to _OneNote_ (its just the driver, not the app).You can assume that ALL of these commands are from an elevated command prompt. First, we are going to use it to get a list of what is installed, then we will use it to clobber those entries. We are going to use the pnputil command to make this all go away.An instance of this might be something like a keyboard or usb flash drive. There are also built in drivers that don't have unique inf files but are still part of your driver tree.Windows copies this inf to c:\windows\inf and renames it with a name that starts with oem and ends with a unique number like oem25.inf. ![]() In this specific case, The OneNote installer installs a "print queue" driverish thingy from C:\Program Files\Microsoft Office\root\Office16\OneNote\prnms006.inf ![]() A driver author writes an inf to install their goodies.You are playing with driversįirst, I am going to give a brief primer on how this all works. One at a time, right click the OneNote entries and choose "Uninstall device".I am not sure how long these changes will last. After looking at your skill level, I rewrote this post.įirst, the simple worry free way.
0 Comments
Leave a Reply. |