C-dev Technologies Inc.

On every restart of my Windows Server 2012r2 x64  system I would get a number of errors about the Microsoft enhanced Point and Print compatibility drivers. After a number of failed attempts I found a solution that worked posted by OveDR. I’m going to reprint his solution here since there was some typos that I found.

• KB3000850(Nov’2014), KB3013769(Dec’2014)

  Installing printer driver Microsoft enhanced Point and Print compatibility driver failed

  Step by step (for x64)
  1. Uninstall KB3013769, restart PC
  2. Uninstall KB3014442 and KB3000850, restart PC
  3. Re-install KB3000850 (includes KB3014442), restart PC

  * KB3000850 has a bug where the following 5 files are not updated.

  4. Open Command Prompt (cmd.exe) (Admin mode)

  net stop Spooler

  copy %windir%\WinSxS\amd64_ntprint.inf_31bf3856ad364e35_6.3.9600.17415_none_2c0b97e88e705434\Amd64\PS5UI.DLL %windir%\System32\spool\drivers\x64\3\PS5UI.DLL

  copy %windir%\WinSxS\amd64_ntprint.inf_31bf3856ad364e35_6.3.9600.17415_none_2c0b97e88e705434\Amd64\PSCRIPT5.DLL %windir%\System32\spool\drivers\x64\3\PSCRIPT5.DLL

  copy %windir%\WinSxS\amd64_ntprint.inf_31bf3856ad364e35_6.3.9600.17415_none_2c0b97e88e705434\Amd64\UNIDRV.DLL %windir%\System32\spool\drivers\x64\3\UNIDRV.DLL

  copy %windir%\WinSxS\amd64_ntprint.inf_31bf3856ad364e35_6.3.9600.17415_none_2c0b97e88e705434\Amd64\UNIDRVUI.DLL %windir%\System32\spool\drivers\x64\3\UNIDRVUI.DLL

  copy %windir%\WinSxS\amd64_ntprint.inf_31bf3856ad364e35_6.3.9600.17415_none_2c0b97e88e705434\Amd64\UNIRES.DLL %windir%\System32\spool\drivers\x64\3\UNIRES.DLL

  net start Spooler

  5. Re-install KB3013769, restart PC

  * KB3013769 has a bug where it doesn’t update the following registry key: [KEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Print\Environments\…….\Microsoft enhanced Point and Print compatibility driver]

  6. Copy all text & save to XXXX.reg file, after double-click install it.

  ↓━━━━━━━━━━━━━━Copy all━━━━━━━━━━━━━━━━↓
  Windows Registry Editor Version 5.00

  [HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Print\PackageInstallation\Windows NT x86\DriverPackages\prnms003.inf_x86_2612b38ce6fb0ccb]
  “DriverStorePath”=”C:\\WINDOWS\\System32\\DriverStore\\FileRepository\\prnms003.inf_x86_2612b38ce6fb0ccb\\prnms003.inf”
  “CabPath”=”C:\\WINDOWS\\system32\\spool\\DRIVERS\\W32X86\\PCC\\prnms003.inf_x86_2612b38ce6fb0ccb.cab”

  [HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Print\PackageInstallation\Windows x64\DriverPackages\prnms003.inf_amd64_2438fbe64075076f]
  “DriverStorePath”=”C:\\WINDOWS\\System32\\DriverStore\\FileRepository\\prnms003.inf_amd64_2438fbe64075076f\\prnms003.inf”
  “CabPath”=”C:\\WINDOWS\\system32\\spool\\DRIVERS\\x64\\PCC\\prnms003.inf_amd64_2438fbe64075076f.cab”

  [-HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Print\PackageInstallation\Windows NT x86\DriverPackages\prnms003.inf_x86_48858e330b88a3d7]

  [-HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Print\PackageInstallation\Windows x64\DriverPackages\prnms003.inf_amd64_864418199e8fa69d]

  [HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Print\Environments\Windows NT x86\Drivers\Version-3\Microsoft enhanced Point and Print compatibility driver]
  “InfPath”=”C:\\WINDOWS\\System32\\DriverStore\\FileRepository\\prnms003.inf_x86_2612b38ce6fb0ccb\\prnms003.inf”
  “DriverVersion”=”6.3.9600.17480”
  “MinInboxDriverVerVersion”=”6.3.9600.17480”

  KEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Print\Environments\Windows x64\Drivers\Version-3\Microsoft enhanced Point and Print compatibility driver]
  “InfPath”=”C:\\WINDOWS\\System32\\DriverStore\\FileRepository\\prnms003.inf_amd64_2438fbe64075076f\\prnms003.inf”
  “DriverVersion”=”6.3.9600.17480”
  “MinInboxDriverVerVersion”=”6.3.9600.17480”

  ↑━━━━━━━━━━━━━━━End Copy all━━━━━━━━━━━━━━━↑

  7. Open Command Prompt (cmd.exe) (Admin mode)

  net stop Spooler

  copy %windir%\WinSxS\amd64_prnms003.inf_31bf3856ad364e35_6.3.9600.17480_none_4389c29fa7dabd7c\Amd64\PrintConfig.dll %windir%\System32\spool\drivers\x64\3\PrintConfig.dll

  copy %windir%\WinSxS\amd64_prnms003.inf_31bf3856ad364e35_6.3.9600.17480_none_4389c29fa7dabd7c\Amd64\unishare.gpd %windir%\System32\spool\drivers\x64\3\unishare.gpd

  copy %windir%\WinSxS\amd64_prnms003.inf_31bf3856ad364e35_6.3.9600.17480_none_4389c29fa7dabd7c\Amd64\unishare-pipelineconfig.xml %windir%\System32\spool\drivers\x64\3\unishare-pipelineconfig.xml

  copy %windir%\WinSxS\x86_prnms003.inf_31bf3856ad364e35_6.3.9600.17480_none_e76b271bef7d4c46\I386\PrintConfig.dll %windir%\System32\spool\drivers\W32X86\3\PrintConfig.dll

  copy %windir%\WinSxS\x86_prnms003.inf_31bf3856ad364e35_6.3.9600.17480_none_e76b271bef7d4c46\I386\unishare.gpd %windir%\System32\spool\drivers\W32X86\3\unishare.gpd

  copy %windir%\WinSxS\x86_prnms003.inf_31bf3856ad364e35_6.3.9600.17480_none_e76b271bef7d4c46\I386\unishare-pipelineconfig.xml %windir%\System32\spool\drivers\W32X86\3\unishare-pipelineconfig.xml

  net start Spooler

  8. Restart PC

  9. Thanks to this fix, Windows will create  a new version of the “Microsoft enhanced Point and Print compatibility driver” CAB

  %windir%\System32\spool\drivers\W32X86\PCC\prnms003.inf_x86_2612b38ce6fb0ccb.cab
  and
  %windir%\System32\spool\drivers\x64\PCC\prnms003.inf_amd64_2438fbe64075076f.cab

I use MySql on my Windows Server 2012r2 x64 system and was getting this warning on every restart:

The syntax ‘–default-character-set’ is deprecated and will be removed in a future release. Please use –character-set-server instead.

The solution that worked for me I found posted by Jon Webb and that was to edit the my.ini file in the MySQL Server 5.1 folder and change both instances of “default-character-set=utf8” to “character-set-server=utf8”.

I had this error every time I restarted Windows Server 2012r2 x64.

The print spooler failed to share printer xxx with shared resource name xxx. Error 2114. The printer cannot be used by others on the network.

After trying a number of different solutions, the one I found that finally worked was posted by J.H. de Baat which was to simply change Computer Browser to start automatically via Services.msc.

My first server was a PowerEdge 600sc that I bought in 2003. At the time Dell was very free with coupons and the total cost was about $270. It came with a 128MB of registered ECC RAM and a 40GB hard disk and a P4- 2.4GHz. I liked the fact that the Dell had a ServerWorks chipset, but unfortunately there was no hardware RAID at that price. There was, however, six IDE ports so a software raid was possible.

I had an MSDN membership which included a license for Windows Server 2003. I configured the server as a Domain Controller.

The 600sc served me well until late 2011 when I finally decided to upgrade. The 600sc was still working but it had become quite loud and instead of repairing it I decided to replace it with its 2011 equivalent, the PowerEdge T110 II. The total cost of the T110 II was about $350 and after shipping and tax still came in under $400. It was configured with 2GB of DDR3 133MHz UDIMMs, an HE253GJ 250GB hard disk and a Xeon E3-1230 3.20 GHz. The E3-1230 is a hyper-threaded quad core so quite a step up from the P4-2.4GHz. There is also a rudimentary built-in RAID, a PERC S100, that would work fine for mirroring the boot drive so I picked up another Samsung HE253GJ for $65 on eBay. For the data drive I installed a Western Digital green 2 TB drive. I also added a Gigaware® 2-Port USB 3.0 PCIe Card and a USB Fax Modem.

I still had an MSDN membership so I went with Windows Server 2008. I did an upgrade and not a clean install so I continued to configure the server as a Domain Controller.

Windows Server 2008 worked fine until I purchased a USB 3.0 3TB external drive for bare metal backups in 2013. I discovered at this point that Windows Server 2008 did not support drives larger than 2TB with 4k sector size but Windows Server 2012 did.

I continued to have an MSDN membership so the server OS of choice became Windows Server 2012r2. I decided to do a clean install when I went to Windows Server 2012r2 and took the opportunity to move away from the Domain Controller and go with a Workgroup. I tested out the bare metal backup using Windows Server Backup and it worked as expected with the caveat that I needed to have the PERC S100 driver available for the re-installation of the server.

The T110 II took the upgrade to Windows Server 2012r2 without a hitch except for the USB Fax Modem. I could receive faxes but could not send them which was a problem since I only needed the Fax Modem it to send faxes. To receive faxes I had a free online account at eFax. The error was that the line was always busy even when it wasn’t. I tried a number of fixes including the fxst30.dll repair and nothing seemed to work so I replaced the USB Fax Modem with a PCIe Fax Modem which fixed the problem.