Wrong SystemRoot variable causes 0xC0150004

Last week I had experienced this quite "funny" situation on WinXP machine.

When I have run some post-build scripts using Jenkings & Maven I have obtained something like:

CMD is not known, not an executable file etc...

I took a look at it and I taught to myself - the "SystemRoot" variable is not set! I have to correct this and it will work fine. Actually this is not true, but apparently it Jenkins does some cleaning in the variables, so it might happend, that the scripts runned by Jenkins will not work as you have expected. Anyway that is not the point of my story. So what I did to "correct" the error was to add the following variable to my USER environement variables:

SystemRoot = SystemRoot\System32

I was too quick and too naive. First the SystemRoot had been already defined in the System variables and second the correct path is just C:\Windows. So I have used this recursion to define the varible - in wrong path.

When I have saved my master work, I could not execute almost any new program. I have always obtained the following error:

0xC0150004

So after a fast google I have found out, that this error appears when the SystemRoot variable is not correctly set. Cool so how to fix the mistake? You cannot launch any program or system utility at all and you need to correct the environement variable.

Well after a wail I have found this solution:

• Login as another user
  
• Start the CMD as the user with the wrong environement variable
• Correct the variable using: SET SystemRoot=C:\Windows
  
• Now you think it is ok, but after a restart you will find out, that the new settings is never taken into account. So do not bother to restart and try the following:
  
• Run REGEDIT from the CMD which is opened using the account and where ther correct SystemRoot was set. Notice it will run....and before it was failing because regedit is dependent on that SystemRoot variable.
  
• Find the user variables searching here: HKEY_CURRENT_USER\Environment
  
• Now correct the SystemRoot variable and voila after restart you can log in again with the "infected account"

The moral of the story:

Lot of applications (notepad, regedit, explorer, task manager) would not start if the SystemRoot is not set correctly.

WinXP will let you set the variable to such a nonsence as:
SystemRoot = SystemRoot\System32

Windows 7 SP1 - Error 80073712

I have obtained the Error with code: 80073712 yesterday while installing Service Pack 1 of Windows 7. I have no idea what was causing the problem, I have fixed it by installing the following update:

http://support.microsoft.com/kb/947821

After installation of this pack, SP1 installed without problems.

Also I have run the System File Checker, which found some errors, repaired them, but also found some errors which he could not repair. So I don't know if it contributed to the fix of the problem.

http://www.microsoft.com/resources/documentation/windows/xp/all/proddocs/en-us/system_file_checker.mspx?mfr=true

Shrew VPN Client Windows 7 - 64 bit

Like many other people on the internet I had to use Cisco VPN Client to connect to our network. First Cisco didn't support 64 bit, now they do support, but I am unable to install the 64bit client. I get this error during the installation:

Installation ended prematurely because of an error.

Well I am using Shrew VPN Client which is freeware and allows to import the Cisco Client pcf configuration files.

After the import and first try to connect it ended up just with "bringing up tunnel ...".
I had to make one more manual step: Uncheck and Check again the Shrew Soft Lightweight Filter on the connection properties tab. (Configure the connection which connects you to internet).



After that everything worked ok for me.