germaconnections.blogg.se

Old xp computer is asking to register windows
Old xp computer is asking to register windows




  1. OLD XP COMPUTER IS ASKING TO REGISTER WINDOWS INSTALL
  2. OLD XP COMPUTER IS ASKING TO REGISTER WINDOWS VERIFICATION
  3. OLD XP COMPUTER IS ASKING TO REGISTER WINDOWS SOFTWARE
  4. OLD XP COMPUTER IS ASKING TO REGISTER WINDOWS MAC
  5. OLD XP COMPUTER IS ASKING TO REGISTER WINDOWS WINDOWS

When you switch environments, WPA thinks you are completely changing computers and requires reactivation.

old xp computer is asking to register windows

OLD XP COMPUTER IS ASKING TO REGISTER WINDOWS WINDOWS

This is because each copy of Windows can only handle one WPA file and can only be installed on one PC. Even if you were to pay MS an additional $300 you would still be where you started if you are trying to virtualize a physical partition, you would just be out $300. The fact that a call to MS tech support will result in them telling you that you will need two copies of Windows when virtualizing shows a lack of understanding as well as a lack of a clear solution. It’s clear that Microsoft did not foresee these problems and still fails to address them.

OLD XP COMPUTER IS ASKING TO REGISTER WINDOWS SOFTWARE

WPA has in no way eliminated piracy and problems like this many times lead users to ditch legal software and go the route of pirated software which isn’t infested and crippled with WPA. Nevertheless, the fact that users need to go through this process to get their systems working is beyond stupid. Windows should now automatically choose the right WPA files and not require activation as you restart or change from physical to virtual hardware. Choose “activation.bat” as the script to add. Go Start>Run>gpedit.msc>Computer Configuration>Windows Settings>Scripts>Startup>Add

old xp computer is asking to register windows

Save the file as “activation.bat” in C:\ Ipconfig /all | find "VMware" > network.tmpįor /F "tokens=14" %%x in (network.tmp) do set vmware=%xĬopy C:\\Windows\\System32\\vmware\\wpa.* C:\\Windows\\System32 The easiest way to do this is to setup a script that will be run when Windows boots: You now have a copy of the WPA info for both your physical and virtual hardware! The next step is to guide Windows to use the right set of files when booting. Copy and paste wpa.dbl and wpa.bak from C:\Windows\System32 into the new “vmware” folder Create a new folder and name it “vmware” Go ahead and reactivate your copy, this can be as simple as doing it through the web or going through a 10 minute phone call with Microsoft’s automated machine. You will be prompted to activate your copy of Windows. Copy and paste wpa.dbl and wpa.bak from C:\Windows\System32 into the new “nativeboot” folderīoot into Linux. Create a new folder and name it “nativeboot” You will be prompted to activate your copy of Windows (if already activated, skip activation and just copy the files). Linux users can follow the steps below to achieve the same results.īoot into Windows XP natively.

OLD XP COMPUTER IS ASKING TO REGISTER WINDOWS MAC

I set out to write a script in Linux to perform this but ran into a much simpler solution that a Mac user developed. You will have WPA files for your native hardware and WPA files for your virtual hardware, just swap prior to boot.

old xp computer is asking to register windows

This means that if you replace the WPA files prior to booting based on whether you’re using VMware or booting natively you won’t have to reactivate. If you go through the activation process in Windows natively as well as under VMware you will notice that the file size changes each time you reactivate. Reading up on WPA I learned that there are two files used to store the hardware info along with WPA data, WPA.dbl and WPA.bak (These files reside in C:\Windows\System32). This meant that I was calling up MS every time I wanted to boot in a different environment hardly practical considering it takes 10 minutes each time activating over the phone. Remember that WPA (Windows Product Activation) typically allows you to reactivate twice through the internet and after that it requires you to call in. I found myself experiencing the same problem others had mentioned I would boot natively and be asked to reactivate, it would work fine until I booted the VM and was again asked to reactivate. that was until I upgraded my hard drive this week. Regardless, I couldn’t really help since I couldn’t reproduce the problem. Really? Maybe he should have read the user’s question more carefully. My favorite answer had to be this one from a Microsoft tech saying “Running a virtual machine counts as running two copies of Windows”. I wasn’t sure what to tell readers and a web search brought up an endless number of forums with the same problem but no answers. I received a lot of complaints from people saying that they were then again asked to reactivate Windows again once they booted back into Windows natively, and then again under VMware and so on every time the OS was booted in a different environment.

OLD XP COMPUTER IS ASKING TO REGISTER WINDOWS VERIFICATION

All this required was to enter the product key, request verification and within a couple seconds everything ran fine.

OLD XP COMPUTER IS ASKING TO REGISTER WINDOWS INSTALL

When I first setup my VMware Server to run an existing Windows Install from a physical partition, I was asked to reactivate Windows XP before I could use it as a guest OS.

old xp computer is asking to register windows

(Time required = 30 minutes) Scroll down to Setting up Automatic Activation to see the process if you are not interested in the background.






Old xp computer is asking to register windows