Need help with Vista re-activation headaches?

[flipdoubt]

I recently had to reactivate my Vista VM after having my MBP serviced. I did it and Vista said I was activated. This morning I got a popup message saying "Windows needs to be activated due to a hardware change." But I did nothing to my hardware nor did I change any of the VM settings. Why would this happen? Is there anything I can do?

Now I have three days to activate when I was activated just fine yesterday. Is there any log to figure out what Vista thinks may have changed?

[WoodyZ]

It may be to late and even if the information can be ascertained it may not help and only cause having to Activate again however if specifically the target Virtual Machine's MAC address and also UUID (although UUID shouldn't effect Activation) are reset to the values prior to you saying 'I copied it" that would be the only thing I can think of at the moment. That information can be gleaned from the vmware.log files in the target Virtual machine's Package providing you haven't restarted it more then a couple times. If you want have a look at and specifically the "Collect vmware.log files" section and archive and attach the archive.zip to a reply post.

[flipdoubt]

Here are the two most recent vmware.log files. Thanks for the help.

I haven't upgraded to 2.0.3 yet, though I have downloaded it into my hot little hands. Should I hold off on upgrading?

Attachment(s)

Archive.zip   113 KB 1 version

[WoodyZ]

Is that all there was was 2 vmware*.log file in the Virtual Machine's Package? If yes then okay but if not why wouldn't you send all 4? Anyway the MAC Address is the same in both that you sent so if you do not have any more the issue is mute.

[flipdoubt]

So we will never know what caused the re-activation and whether it will happen again ... right?

[cdc1]

Check your windows event logs, if I remember right the activation logs are kept in the "Application" logs area in event viewer. Multiple activation attempts can be caused by a problem with windows not being able to update it's hardware "signature". It'll assume it's not a valid copy of Windows if this happens a few times in a row, forcing the "Activate in 3 Days" scenario.

Of course, this is just one of the things that can cause the behavior that you're experiencing.

[flipdoubt]

Hmmm, maybe it was my choice to choose "copy" rather than "move" in the original topic. Last night I upgraded Fusion to 2.0.3. Then I physically moved my VM out of "_{/Library/Application Support/VMware Fusion/Virtual Machines" to "}/Documents/Virtual Machines". When I started the VM, Fusion asked whether I copied or moved; I choose moved; and now my Vista VM says "Windows is activated" with no actions on my part inside the VM. Weird.

[flipdoubt]

It just happened again, where Vista complained the hardware has changed

and the OS needs to be reactivated. I did nothing but restart my VM

after Vista applied some Windows updates.

Here are all four log files.

Attachment(s)

vmware.log.zip   72 KB 1 version

[smsharma]

I am no expert in this matter but Vistal EULA specifically limits it's use as a VM!

[flipdoubt]

Huh? It is Vista Ultimate (which I believe can be virtualized) that I have been running in the same VM since Fusion was in beta. I had no reactivation problems until a few weeks ago when I brought my Mac in for service, after which I successfully reactivated. Now, after no hardware changes at all, Vista seems to have forgotten ...

Can anyone look at those log files?

[WoodyZ]

Suggest you read the EULA! Have a look at: Find End User License Terms for Microsoft Software Licensed by Microsoft or the Computer Manufacturer

From Windows Vista_Home Basic and Home Basic SP1, Supplemental_English_5d0d2c2e-c446-4720-bf62-ce1ed6b7e0af.pdf

MICROSOFT SOFTWARE SUPPLEMENTAL LICENSE TERMS

WINDOWS VISTA HOME BASIC, HOME PREMIUM, BUSINESS, ULTIMATE, AND THEIR SERVICE PACK 1 VERSIONS

>

If you are licensed to use Microsoft Windows Vista Home Basic, Home Premium, Business, or Ultimate, or Service Pack 1 of any of these Windows Vista editions (the “software”), you have the following license right. If there is a conflict with any past or future license terms for the software, this supplemental license term applies.

Use with Virtualization Technologies. Instead of using the software directly on the licensed device, you may install and use the software within only one virtual (or otherwise emulated) hardware system on the licensed device. When used in a virtualized environment, content protected by digital rights management technology, BitLocker or any full volume disk drive encryption technology may not be as secure as protected content not in a virtualized environment. You should comply with all domestic and international laws that apply to such protected content.

I am no expert in this matter but Vistal EULA specifically limits it's use as a VM!

[flipdoubt]

I swear I did not change anything about how my VM is configured, but Vista's Performance Information and Tools window now says the VM has 1 processor core whereas I thought it used to say 2. Fusion supports dual virtual processors, right? I'm pretty sure I set this to 2. I wonder what will happen if I shut down and set that back to two. Has anyone ever observed Vista to remember an old configuration and recognize that the machine has returned to that configuration? Could the Apple service visit have caused Fusion to reset the VM to two cores?