![]() If you include the above in your package, there should not be any issues. The is a dependency to wusa.exe and has to be located in the appropriate language folder off the root of the folder the EXE is located in, for example. The errors and failures that everyone is receiving is in relation to the MUI or language pack not being available. This is what I have identified above and beyond what everyone else has commented on regarding the use of wusa.exe (WUSA - Windows Update Standalone Installer). I was scowering all over the web for a solution. Has anyone else found and solved this? Is it some weird problem with. I've also tried explicitly Exec'ing and ShellExec'ing wusa.exe, with no difference. Running from the elevated UAC version of the installer produced the same result, as did explicitly setting UAC::RunElevated and/or using UAC::ShellExecWait. I just spent a few hours trying to get the UAC addin to help it did not. ![]() This is odd, since the installer itself elevates (prompt and everything) and can write to the Program Files directory.Īll the documentation I can *find* suggests that it should exec programs as Administrator. Some flailing around eventually got it to admit it was failing because it wasn't running as Administrator. It does what's expected on XP (so I know the download works and the installer is basically correct). It wants to run on Vista and download and install Windows Installer 4.5 as a shiny.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |