Finding the Windows product key VBScript

If you planned to do a reinstall of Windows but you cannot find your Windows product key, you are in luck because the product key is stored in the Windows registry. Follow the following steps to restore the product key:

Step 1: Copy and paste the following into a Notepad window:

Set WshShell = CreateObject(“WScript.Shell”)
MsgBox ConvertToKey(WshShell.RegRead(“HKLM\SOFTWARE\Microsoft\Windows NT\CurrentVersion\DigitalProductId”))

Function ConvertToKey(Key)
Const KeyOffset = 52
i = 28
Cur = 0
x = 14
Cur = Cur * 256
Cur = Key(x + KeyOffset) + Cur
Key(x + KeyOffset) = (Cur \ 24) And 255
Cur = Cur Mod 24
x = x -1
Loop While x >= 0
i = i -1
KeyOutput = Mid(Chars, Cur + 1, 1) & KeyOutput
If (((29 – i) Mod 6) = 0) And (i <> -1) Then
i = i -1
KeyOutput = “-” & KeyOutput
End If
Loop While i >= 0
ConvertToKey = KeyOutput
End Function

Step 2: You will need to use File -> Save As, change the “Save as type” to “All Files” and then name the file as <FILENAME>.vbs where <FILENAME> denotes the name of the file to be saved.

Step 3: Once you have saved the file, you can just double-click on the saved file, and the popup window will show you your product key.

Installing Hyper-V Manager on Windows 7

Recently one of my clients asked me whether it is possible to install Hyper-V Manager on Windows 7. I was puzzled at the question. Upon further questioning my client, I was informed that due to compliance issue they can only install Windows 7 as most of their applications are not certified for Windows 8 and above yet.

After much consideration, I decided to explore whether we can really install Hyper-V Manager on Windows 7. Thanks to Remote Server Administration Tools for Windows 7 with Service Pack 1. There is indeed a way to install Hyper-V Manager on Windows 7. To install Hyper-V Manager on Windows 7, you can follow the following steps:

1. Download and install Remote Server Administration Tools from:
2. Install either the 32-bit or 64-bit versions of the Remote Server Administration Tools depending on what version of Windows 7 you are using.
3. Go to Start, point to Control Panel, and then click on Programs.
4. Next, you will see an option to Turn Window features on or off. Click on this option.
5. Expand Remote Server Administration Tools.
6. Expand Role Administration Tools, find the option for Hyper-V Tools, check the checkbox, and then click OK.
7. We are done! You can now type Hyper-V Manager at the Start Menu or go to Start, point to Administrative Tools, and then click Hyper-V Manager.

Fixing Cisco Systems VPN Client – “Reason 442 Failed Virtual Adapter Error” (Windows 8)

The fix is changing the faulty registry key.

Perform the following steps to apply the fix:

Step 1
If you are on the Windows 8 desktop, point the cursor at the lower right corner of the screen. Click the “Search” option as soon as it pops up on the left-side of the screen. If you are on the Metro UI Start Screen, point the cursor at the lower left corner of the screen and click the right mouse button. Now select the “Search” option on the context menu.

Step 2
When you perform either of the above actions, Windows 8 will load the “Apps” screen. Type “regedit” into the search bar located on the right side of the “Apps” screen.

Step 3
Click the “regedit” search result on the left side of the “Apps” screen. If you see a UAC dialog box, click “Yes” to open the Windows 8 Registry Editor.

Step 4:
Look for the registry entry “HKEY_LOCAL_MACHINE\SYSTEM\CurrentControl­Set\Services\CVirta”.

Step 5:

Change the “Display Name” “@oem11.inf,%CVirtA_Desc%;Cisco Systems VPN Adapter for 64-bit Windows” to “Cisco Systems VPN Adapter for 64-bit Windows”.

That’s all.

Unable to install Windows 8 – Error Code 0x0000005D

When you try to install Windows 8 on a Pentium 4 or lower computer, but upon boot, you are getting the following error message:
Your PC needs to restart
Please hold down the power button
Error Code 0x0000005D

Unlike Windows 7 and its predecessors, Windows 8 is not compatible with all models of the Pentium 4 processor.

This is due to the fact that Windows 8 requires a processor compatible with the following functions: SSE2, PAE and NX bit. All Pentium 4 are compatible with SSE2 and EAP: the problem may come from the NX bit.