A MS-DOS script executes the VBScript below and it works fine. However, when using a MS Build master deployment file which calls the aforementioned MS-DOS script, the 2nd location lookup ("SOFTWARE\Microsoft\Windows\CurrentVersion\Installer\UserData\S-1-5-18\Products\") fails with a result code of 2. I have spent countless hours trying to figure out why the difference. Any ideas?

Const HKLM = &H80000002 'HKEY_LOCAL_MACHINE
Set oRegistry = GetObject("winmgmts:{impersonationLevel=impersonate}!\\" & node & "/root/default:StdRegProv")

REM 1st location: "SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall\"
sBaseKey = "SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall\"
iRC = oRegistry.EnumKey(HKLM, sBaseKey, arSubKeys)
If iRC <> 0 THEN
WScript.Echo "Registry lookup failed for " & sBaseKey
ELSE
For Each sKey In arSubKeys
iRC = oRegistry.GetStringValue(HKLM, sBaseKey & sKey, "DisplayName", sValue)
If sValue = Wscript.Arguments.Item(1) Then
oRegistry.GetStringValue HKLM, sBaseKey & sKey, "UninstallString", sValue
InstalledApplications = Replace(sValue, "/I{", "/X{")
IF LEN(InstalledApplications) > 0 THEN
InstalledApplications = InstalledApplications & " /qn /l*vx """ & sFile & ".Log"""  & Chr(13) & Chr(10) 
END IF
END IF
NEXT
END IF

REM 2nd location: "SOFTWARE\Microsoft\Windows\CurrentVersion\Installer\UserData\S-1-5-18\Products\<GUID>\InstallProperties"
arProducts = NULL
sBaseKey = "SOFTWARE\Microsoft\Windows\CurrentVersion\Installer\UserData\S-1-5-18\Products\"
iRC = oRegistry.EnumKey(HKLM, sBaseKey, arProducts)
If iRC <> 0 THEN
WScript.Echo "Registry lookup failed for " & sBaseKey
ELSE
For Each guid In arProducts
sInnerKey = sBaseKey & guid & "\InstallProperties\"
iRC = oRegistry.GetStringValue(HKLM, sInnerKey, "DisplayName", sValue)
If sValue = Wscript.Arguments.Item(1) Then
oRegistry.GetStringValue HKLM, sInnerKey, "UninstallString", sValue
InstalledApplications = Replace(sValue, "/I{", "/X{")
IF LEN(InstalledApplications) > 0 THEN
InstalledApplications = InstalledApplications & " /qn /l*vx """ & sFile & ".Log""" & Chr(13) & Chr(10) 
END IF
END IF
NEXT

InstalledApplications = InstalledApplications & "GOTO:EOF"

64/32 bit execution environments.  Default build for VS is 32 bit.

You need to ask this kind of question in the developers forum.

64/32 bit execution environments.  Default build for VS is 32 bit.

You need to ask this kind of question in the developers forum.

Depends on how you are executing MSBuild.

Again - this is a question for the developer forum.  It is not a scripting issue as you have already proven that the script works.

Think about the issue. What does returncode 2 mean and why might you get it.  Either the path does not exist or you are looking at the wrong registry view.

Try this:

c:\windows\system32\cscript <yourscript>

and

c:\windows\SysWow64\cscript <yourscript>

One should succeed and the other fail.

Think about the issue. What does returncode 2 mean and why might you get it.  Either the path does not exist or you are looking at the wrong registry view.

Try this:

c:\windows\system32\cscript <yourscript>

and

c:\windows\SysWow64\cscript <yourscript>

One should succeed and the other fail.

There is no DOS. Cmd.exe is a Win32 console program that, despite appearances, has nothing whatsoever to do with DOS.

Think about the issue. What does returncode 2 mean and why might you get it.  Either the path does not exist or you are looking at the wrong registry view.

Try this:

c:\windows\system32\cscript <yourscript>

and

c:\windows\SysWow64\cscript <yourscript>

One should succeed and the other fail.

Think about the issue. What does returncode 2 mean and why might you get it.  Either the path does not exist or you are looking at the wrong registry view.

Try this:

c:\windows\system32\cscript <yourscript>

and

c:\windows\SysWow64\cscript <yourscript>

One should succeed and the other fail.

Those keys are not visible form the 32 bit version of MSBuild and Visual Studio,  You must run from a 64 bit session to access the 64 bit registry.  Change your build environment to 64 bits and try it.

Or try sysnative:

https://msdn.microsoft.com/en-us/library/windows/desktop/aa384187%28v=vs.85%29.aspx

Or try sysnative:

https://msdn.microsoft.com/en-us/library/windows/desktop/aa384187%28v=vs.85%29.as

Or try sysnative:

https://msdn.microsoft.com/en-us/library/windows/desktop/aa384187%28v=vs.85%29.as