Archive for January, 2013

My nephew gets all his skills from me. look out pro-bowlers. No really,  look out, no telling where that thing will land…

I have been using Google Drive seriously for about a year. Making sure to work off the cloud as much as possible. Until now, I have not had any real issues, although, I’ve noticed that Google Drive is much slower than Drop Box, mainly do to the difference in how Google drive and drop box index your files. Regardless, the problem I am having now is probably a deal breaker. Google Drive is crashing my nice new Windows 8 install on my Dell Optiplex 960.

I installed the pre-release of Windows 8 a couple of months ago. Since I have been extremely satisfied with it, I decided to take advantage of Microsoft’s $39.99 deal and upgrade all my machines. The one program I didn’t really test was Google drive, since that runs on my little HP mini laptop that I strictly use for backups. Now that I have a shiny new 2 TB Seagate drive in my Optiplex, I want to use this machine for my backups. I installed drop box and Google drive. The computer restarted once and two other times it informed me that Google drive was having an issue.

Now I would look into this a little bit more, but apparently in December of 2012, Google made it very clear they were not planning on building any new apps for it. “We have no plans to build out Windows apps,” said Clay Bavor, product management director at Google Apps. Apparently, they are not planning on supporting it either.

FYI, I am running the 64 bit version of Google Drive and Windows 8.

Here is the error from my system log:


Log Name: Application
Source: Application Error
Date: 1/22/2013 12:56:33 PM
Event ID: 1000
Task Category: (100)
Level: Error
Keywords: Classic
User: N/A
Computer: garage
Faulting application name: googledrivesync.exe, version: 1.7.4018.3496, time stamp: 0x509418e4
Faulting module name: python26.dll, version: 2.6.4150.1013, time stamp: 0x4ae54ea8
Exception code: 0xc0000005
Fault offset: 0x00025e10
Faulting process id: 0xc94
Faulting application start time: 0x01cdf8c865f26729
Faulting application path: C:\Program Files (x86)\Google\Drive\googledrivesync.exe
Faulting module path: C:\Users\Bill\AppData\Local\Temp\_MEI31562\python26.dll
Report Id: 0e26374f-64bd-11e2-be6c-0024e837d4ac
Faulting package full name:
Faulting package-relative application ID:
Event Xml:
<Event xmlns=””>
<Provider Name=”Application Error” />
<EventID Qualifiers=”0″>1000</EventID>
<TimeCreated SystemTime=”2013-01-22T17:56:33.000000000Z” />
<Security />
<Data>C:\Program Files (x86)\Google\Drive\googledrivesync.exe</Data>

There is a little known “gotcha” when upgrading to Windows 8 from Windows XP.

Microsoft doesn’t make it real well known, that if you upgrade from Windows XP 32 bit to Windows 8, you will end up with the 32 bit version of of Windows 8. You will not get the option to install the 64 bit version “even” if your system is 100% compatible. Really it isn’t the fact that its XP, it’s the fact that it is a 32bit version of the operating system, it can be Vista, Window 7, or any other 32 bit operating system.

This was verified on a Dell Optiplex 745 and a Dell Optiplex 960.

What I did, was actually call Microsoft, explain the situation and simply cancel my order. Then I installed the Trial/beta/pre-release edition of Windows 8 64 Bit which allowed me to upgrade to a legal licensed copy of Windows 8 64 Bit.

After much research, I was able to find this on Microsoft’s website. Which means until January 31st, 2013 instead of paying the special upgrade price of $39.99, Microsoft will get you for the DVD version at $69.99, which is still a fair price for an operating system. You could always do what I did and install a 64 bit version first though. Regarding the special upgrade price, see this article.


Can I upgrade from a 32-bit version of Windows to a 64-bit version of Windows 8?
Yes, but you can’t do this using Upgrade Assistant. If your PC has a 64-bit capable processor (CPU) but is currently running a 32-bit version of Windows, you can install a 64-bit version of Windows 8 Pro, but you’ll need to buy it as a DVD and perform a custom installation. If available in your country or region, you can buy Windows 8 Pro from a participating retail store. You can also buy it online from the Microsoft Store in Austria, Belgium, Canada, France, Germany, Ireland, Italy, Japan, Netherlands, Spain, Switzerland, United Kingdom, and United States.
Please note that the Windows 8 Pro Pack is used to upgrade from Windows 8 to Windows 8 Pro, and is not for cross-architecture installs and does not include any media. If you want to change architectures, purchase Windows 8 Pro.
You won’t be able to keep any files, settings, or apps when you upgrade from a 32-bit to a 64-bit version.”

If you are dying to get Windows 8 and don’t want to break the bank, you better hurry up. Microsoft has Windows 8 at a introductory offer of only $39.99! That price is for the download version of Windows 8. If you would rather have a retail disk, that will cost you $69.99 for a DVD (free standard shipping). Also, as a Bonus you receive the Pro version, Microsoft is really pushing their new operating system and I think this is a great way to convert a lot of the slower to adopt users.

Personally, I have 3 machines to upgrade before the final day, so I will report back how the process goes. According to Microsoft, it is a simple upgrade. Installing the beta release candidate could not have been easier, so I don’t imagine this will be a problem.

Downloading the upgrade is easy, simply go to

  • Click Download Pro to install Windows 8 Upgrade Assistant. Depending on your Internet connection, the installation might take several minutes.
  • When prompted by your browser, open, save, or run Upgrade Assistant. You must run Upgrade Assistant to purchase Windows 8 Pro, but you can also run it without purchasing.
  • Follow the instructions in Upgrade Assistant to find out if your PC can upgrade to Windows 8 Pro, and then follow the steps to purchase, download, and install. For more detailed information, see How to download Windows 8 orUpgrade to Windows 8.

Check back or sign up for an email alert at the bottom of this page to see how my upgrades go.


Recently we had a problem with very slow logons to one of the Terminal Servers. The terminal server is currently running Windows 2003 Server, but I would bet it could be the same problem on 2008 or even Windows Server 2012.

The problem is with printer caching, usually bloated drivers that get cached when a user logons. HP is famous for having bloated drivers, but Sharp is pretty bad too. We use mostly Sharp copiers across our facility, many, many copiers and lots of Brother printers.  Basically it is a few minute quick fix to get your server working again and then we will automate the process so you can set it and forget it. All we will be doing is deleting a couple of registry keys, so no need to worry, this doesn’t affect drivers or anything, these keys are automatically recreated. Just check these keys and see if you have hundreds or even thousands of entries, if so, you can manually delete the key and your server will return to its lightning fast self. It’s easier and faster to use the script below though.

NOTE: Be patient, the first time we did this it took between 20 and 30 minutes to delete just one key. Also, you will notice if people are currently logging in or logged on that not all entries will be removed, that’s completely fine.

HKEY_CURRENT_USER\Software\SHARP HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Terminal Server\Install\Software\SHARP

If you have HP copiers, then you will see these keys instead.

HKEY_CURRENT_USER\Software\Hewlett-Packard HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Terminal Server\Install Software\Hewlett-Packard

This is a temporary fix, I highly recommend creating the cleanup scripts below to make it a permanent solution. I will attach mine to this article, feel free to download and use them, at your own risk of course, but you will notice they are basic one or two line scripts that simply remove some registry keys. If you are worried just backup the key first.

You will need two scripts, one to call a registry deletion of HKLM and HKU, and the other will call the key deletion of HKCU. We put our scripts in the system32 folder so if you put your script else where, just update the location in the script. This is all really basic stuff so I’m not going to go into too many details.

First, Logon as an Admin user and follow the steps below:

Create script in C:\Windows\system32\ called “CleanupSharp.bat” with this code in it:

regedit /s C:\Windows\system32\CleanupSharp.reg

Create a reg file in C:\Windows\system32\ named “CleanupSharp.reg” with this text in it:

Windows Registry Editor Version 5.00
[-HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Terminal Server\Install\Software\SHARP]

At this point, simply run the CleanupSharp.bat script to get your Terminal Server responding normally again. Then move on to the steps below to make it as fast as it can be. This cleans the user hives, which helps a lot, but not nearly as much as the first script, it is very important though so don’t skip this step lazy ass.

Create script in C:\Windows\system32\ called “CleanupSharp-user.bat” with this code in it:

regedit /s C:\Windows\system32\CleanupSharp-user.reg

Create a reg file in C:\Windows\system32\ named “CleanupSharp-user.reg” with this text in it:

Windows Registry Editor Version 5.00


Now, Let’s automate the process… see below for a zip file with scripts.

Run or open gpedit.msc and go to Computer Configuration->Windows Settings->Scripts and add “C:\Windows\system32\CleanupSharp.bat” to shutdown scripts.

Then go to User Configuration-> Windows Settings-> Scripts and add the other script C:\Windows\system32\CleanupSharp-user.bat to logoff scripts.

Logon as a regular user and that should remove the SHARP current user key on logoff, make sure you logoff then back on to the machine to verify ;-)

If for some reason nobody is logged on to your Terminal Server you can do a reboot and test the shutdown script removes the other keys.

That’s all there is to it! If you use HP, be sure to change the “SHARP” to “Hewlett-Packard”. If you have other copiers or printers, just check them, if there is a ton of lines in the key, then substitute that name in the reg files.

Now enjoy your like new Microsoft Terminal Server :)

Here is the link to the files TS_Printer_Clean