RegistryProtectedTest Fail with GoogleUpdate about omaha HOT 7 OPEN

The test that is failing is supposed to test that, in the case msxml is not 
available, the function CheckSystemRequirements() returns a specific error. The 
test environment tries to simulate this condition by redirecting the registry 
HKLM hive so that looking up the COM classes defined by msxml would fail. For 
some reason, in this case, the assumption break. It looks like the test has 
succeeded. It may be a bug in the code itself, which can be traced into the 
debugger, or may be that for some reason, msxml is activated somehow despite 
the registry redirection.

My guess is that this unit test isn't being run from an account with 
administrative privileges (or from an elevated command prompt).  If you try to 
run it as a normal user, you won't have permission to redirect HKLM.

Hammer was run from a command prompt as administrator

Thanks for the quick replies, by the way.
I believe I ran the script from a regular command prompt and another as 
administrator and obtained the same results.

Not sure if this is relevant, but when running run_unit_tests.py, there are a 
couple other tests that fail as well:
[ RUN      ] OmahaCustomizationGoopdateComInterfaceTest.TypeLib
C:\omaha/testing/omaha_customization_test.h(71): error: 
::LoadTypeLib(omaha_dll_path, &type_lib_) failed with error 0x80029c4a

[ RUN      ] OmahaCustomizationTest.IsInternalUser
common\omaha_customization_unittest.cc(379): error: Value of: 
ConfigManager::Instance()->IsInternalUser()
  Actual: false
Expected: true
[  FAILED  ] OmahaCustomizationTest.IsInternalUser (1 ms)


The full output is attached. There are failures from 5 different tests.

Also, I do have a Registry Key at HKEY_LOCAL_MACHINE\Software\Google\UpdateDev.
It is called "TestSource" with value "ossdev." 

Note: I have also tried with the value "dev" and have also run this test by 
building a non GoogleUpdate version where the registry key was at 
HKML\Software\OmahaCompanyName\UpdateDev, and got the same results.

Again, not sure if this is entirely related to the previous case. 

I have the same problem.And build omaha with hammer as administrator would not 
solve this issue. using the omaha-src-r110.zip. any ideas? kindly help