I’ve got some Windows virtual machines I use for when I need to do MS Office stuff or a brief bit of Win32 programming, and noticed earlier that each time I reboot Windows, ZoneAlarm Free decides to nag me to upgrade, and there’s no option to switch it off. In fact, I’d go as far as to say they’d gone a bit talkie-toaster… I can see why they’d do it, but I’m not going to upgrade to a full, paid security suite for a virtual machine I fire up only if and when I have to (which isn’t that often) – it’s a no-sale. So I did a bit of googling and found the solution.
The trick is that you need to modify the following registry keys and flip them from 1 to 0:
However, the problem with doing so is that Zone Alarm has these keys locked, and quiting ZoneAlarm doesn’t unlock them, so you need to reboot Windows into Safe Mode to do it by stabbing F8 during boot a few times and then selecting to boot in Safe Mode.
Once you’re in Safe Mode, you can either go and flip the flags manually using regedit, or you could dump the following into a file with a .reg extension and then execute it:
Windows Registry Editor Version 5.00[HKEY_LOCAL_MACHINE\SOFTWARE\Zone Labs\ZoneAlarm]"RunSwitchbackWizard"=dword:00000000
Or, you could download and run a version I created earlier (Right click and Save As…): ZA-NoNag.reg
Done & done.
Credits: Many thanks to oldsod on the ZA forums for the fix!
However, since I run Linux I thought I’d just get a copy of CrossOver and I’d be laughing, but this was not to be. I ponied up for Office, set it downloading, then went to get CrossOver only to find it only supports up to Office 2007 – and I don’t mean that Office 2010 won’t work 100%, or will be a little eratic – it won’t work at all. Feck!
Okay, so I can always run it through virtualisation (i.e. a VirtualBox or VMWare instance running some variety of Windows), but I didn’t fancy running the latest, greatest Office on a shonky old copy of XP, so I ponied up (again) for a copy of Windows 7 64-Bit Upgrade (that’s another $49AUD through It’s Not Cheating) and created a new virtual machine, installed Windows 7, entered the key at the end of the install, and it told me it wasn’t valid! Double feck!
At this point I’m $150AUD out of pocket with nothing to show for it, and am starting to furrow my brow.
Trying to deal with the key issue later – I just left the key out to get 7 up and running (it’ll go for 30 days without activation) and tried the key again from within the OS rather than from the installer; this time instead of just key invalid I got an error message stating that this key is not valid for a clean install of Windows… Okay.. now we’re getting somewhere – let’s fix this bad boy.
There’s a bunch of stuff on the Web about forcing Windows 7 to accept a clean install from an upgrade disc by creating registry keys, running arcane commands (slmgr -rearm etc.), removing config files from the ISO before install etc. – and to be perfectly honest I didn’t fancy re-installing so I had a quick whirl at all of ’em. And guess what? They didn’t work, so I’m not going to post them here. Instead I’ll tell you what worked for me [drumroll please….]:
Installing another version of Windows first.
It doesn’t have to be 64-bit if you’re migrating 32-bit to 64, it doesn’t have to be one step below Windows 7 (i.e. Vista), it doesn’t even have to be a legal, valid version of Windows! It just has to be some incarnation of Bill’s Marvelous Blue-Screen Machine, and then when you install Windows 7 on top of the existing install, it’ll recognise a prior version of Windows existed, and your “upgrade” key will work perfectly.
So in my case, this just meant slapping a copy of XP onto a new virtual machine, then the instant that’s finished installing, just changing over the ISO image mounted on the virtual DVD drive from XP to 7, rebooting, and letting this second version of Windows install.
Once you’ve got Windows 7 up and running, your “old” copy of windows will be sitting in C:\Windows.old, and you can either use the built-in Disk Cleanup tool to remove it or just delete that folder and you’re as good as new*.
* = If you’re doing a native Windows 7 install, once you’ve removed the old install then you’re quite literally good as new. If you’re installing on a virtual box using a hard drive which uses dynamic storage (i.e. you allocate, say, 60GB for the HD, but it doesn’t take up any space to begin with, it only takes up space when data is added to the drive) then the space allocated for the old Windows install can’t be fully recovered because dynamic disks can take up more space, but do not resize back down to take up less space when you remove data! But you’re going to put more than 700MB of additional stuff on it anyway, right? So just remove the old Windows install before installing new apps and the like and you’ll break even!
It’s not a glamorous hack or sneaky workaround, but it does work, and who doesn’t have an old copy of Windows sitting around somewhere? If you’re feeling particularly cheeky you could try it with a copy of Windows 3.1 or 95 installed and see if it still upgrades clean ;-)
Update: I was discussing this with some colleagues the other day who clued me in to the following rather sneaky (but perfectly legitimate) method of installing Windows 7 Upgrade as a “fresh install”:
Install Windows 7 as a fresh install and do not enter your key while installing.
From within your installed and running (but not activated) version of Windows 7, go to your Windows 7 disc and install it again!
If your Windows 7 Update disc doesn’t show setup type stuff (because it’s UDF and there’s all sorts of issues), just reboot the machine and install Windows 7 over Windows 7, um, dawg ;)