Jan 232013

When using a 32bit print server with printers using HP Universal Print driver (HP UPD) and a 64 bit client, it is possible that printers cannot be added.

The problem occures because HP uses a 32 bit path to a file in the printer queu. The x64 client cannot resolve this location and the printer installation fails.

The solution:

First make sure that the 64bit driver is installed on the server. Log on to the print server.

Browse to the following key

[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Print\Printers\PRINTERNAME\CopyFiles\BIDI

Delete the BIDI key. This will not affect 32bit clients. Everything still works. The printer can now be added.

It is better to use a 64bit print server but that isn’t always possible. This doesn’t change anything about the fact that HP makes unstable print drivers. The best solution is to buy better printers not made bij HP. But that’s my opinion.

Jan 112013
  • UPDATED 2012-4-8: The problem got back after re-installing the Site Server with a new database as stated here before in this artikel. Read on to see what caused this problem.

At one point I got an error “Error creating media. Error message is : The hash value is not correct.. Please refer to  to get details.” when creating a standalone tasksequence media ISO.

Continue reading »

Jan 022013

The solution to disable the autoupdate on my previous post, didn’t seem to work in the new Flash version.

So I found another solution. Just remove the update task after installation with the schtask command. I’ve used Installshield to perform this action.
First, Make a new mst. Add all you regular stuff. After that, make a custom action.

Choose New Exe, path referencing a directory.


Fill in as the screenshot above. Save the MST.

This works with both the ActiveX as the plugin version of the installer.

Update: Still works on Flash 11.6.602.171

And if you like copy paste (less errors) you can use

[SystemFolder]Schtasks.exe /Delete /TN “Adobe Flash Player Updater” /f