<html>
<head>
<base href="http://bugzilla.wpkg.org/" />
</head>
<body>
<p>
<div>
<b><a class="bz_bug_link
bz_status_NEW "
title="NEW - Intermittent problem Uninstall not found in System Context"
href="http://bugzilla.wpkg.org/show_bug.cgi?id=287#c8">Comment # 8</a>
on <a class="bz_bug_link
bz_status_NEW "
title="NEW - Intermittent problem Uninstall not found in System Context"
href="http://bugzilla.wpkg.org/show_bug.cgi?id=287">bug 287</a>
from <span class="vcard"><a class="email" href="mailto:r.meier@wpkg.org" title="Rainer Meier <r.meier@wpkg.org>"> <span class="fn">Rainer Meier</span></a>
</span></b>
<pre>(In reply to Robl from <a href="show_bug.cgi?id=287#c7">comment #7</a>)
<span class="quote">> So then the original command "%windir%\System32\cscript.exe /b /nologo
> \\DOMAIN\wpkg\wpkg.js /synchronize /quiet /nonotify /noreboot" would have
> been calling the x64 version of cscript.exe?</span >
Yes it does. Unless called from 32-bit cmd.exe which would force it to be
redirected to SysWoW64\cscript.exe and therefore execute 32-bit cscirpt.exe
again.
So just use "%windir%\System32\cscript.exe /b /nologo \\DOMAIN\wpkg\wpkg.js
/synchronize /quiet /nonotify /noreboot" but absolutely make sure it's run from
64-bit cmd.exe.
If in doubt call %SystemRoot%\sysnative\cscript.exe (if it exists, which is the
case on 64-bit systems only). This is what wrapper.js does. It fixes the
mistake of users running cscript.exe from a 32-bit application and forces to
invoke 64-bit cscript.exe.</pre>
</div>
</p>
<hr>
<span>You are receiving this mail because:</span>
<ul>
<li>You are the QA Contact for the bug.</li>
</ul>
</body>
</html>