[solved] Installation successful but no updates installed

[icnocop]

Hi.

Thank you for wsusoffline v6.6.1.

I tried to install updates on Windows 7 Ultimate x64 using the following command launched from another program:

"d:\windows_7_x64_updates\client\cmd\Doupdate.cmd" /nobackup

The output indicates that the installation was successful, but when I look in "Programs and Features" and "View installed Updates", it does not list any updates.

If I manually run that same command in an elevated command prompt, it works just fine.

I am thinking that the program launcher is not doing something right, so I will look into that, but the problem is that the output indicates that the Installation was successful when really it is not.

Any ideas?

Thank you.

Here is the output:

Code: Select all

Starting WSUS Offline Update (v. 6.6.1)...
Determining system's properties...
Found OS caption: Microsoft Windows 7 Ultimate
Found Microsoft Windows version: 6.1.7600 (w61 x64 enu sp0)
Checking user's privileges...
Checking medium content...
Medium build date: Sat
Medium supports Microsoft Windows (w61-x64 glb).
Checking Windows Service Pack version...
Checking Windows Update Agent version...
Installing most recent Windows Update Agent...
Installing ..\wsus\WINDOWSUPDATEAGENT30-X64.EXE...
Checking Windows Installer version...
Checking Windows Script Host version...
Checking Internet Explorer version...
Checking Microsoft Security Essentials installation state...
Checking state of service 'automatic updates'...
Starting service 'automatic updates' (wuauserv)...
Listing ids of missing updates...
Listing ids of installed updates...
Listing update files...
Info: Skipping update KB976002 due to matching black list entry.
Info: Skipping update KB890830 due to matching black list entry.
Installing updates...
Installing update 1 of 22...
Installing ..\w61-x64\glb\WINDOWS6.1-KB974431-X64_3B5B26EF9CCB63D32DE2065CAD7ADDF85CBAB4A2.CAB...
Installing update 2 of 22...
Installing ..\w61-x64\glb\WINDOWS6.1-KB975467-X64_BEB1354BBA1BE5DE8CDBE68BF537D5DF1618EABB.CAB...
Installing update 3 of 22...
Installing ..\w61-x64\glb\WINDOWS6.1-KB974571-X64_D2F3D4FAB18A871EB5A6EB5F7B7FBB4B7715A439.CAB...
Installing update 4 of 22...
Installing ..\w61-x64\glb\WINDOWS6.1-KB972270-X64_44D2E6541138061257003636909D404CC4675F2C.CAB...
Installing update 5 of 22...
Installing ..\w61-x64\glb\WINDOWS6.1-KB977074-X64_CFEC3A13B71307A1518C894AEAB723CAF30C1EA8.CAB...
Installing update 6 of 22...
Installing ..\w61-x64\glb\WINDOWS6.1-KB975560-X64_A0D3312D011A53695ECABC12954690BFA9E1A230.CAB...
Installing update 7 of 22...
Installing ..\w61-x64\glb\WINDOWS6.1-KB971468-X64_3A3CB2D4CE0F6BB55955BB8098A998B3F125EE49.CAB...
Installing update 8 of 22...
Installing ..\w61-x64\glb\WINDOWS6.1-KB980232-X64_64836E02B35E9140149BB846FA9A65873F59B251.CAB...
Installing update 9 of 22...
Installing ..\w61-x64\glb\WINDOWS6.1-KB979309-X64_373C976AF04D6E07A40208B80B809DE45D3767C5.CAB...
Installing update 10 of 22...
Installing ..\w61-x64\glb\WINDOWS6.1-KB979683-X64_71F2D6D1FBD4881C2150A23DCC96DFFDB37E4965.CAB...
Installing update 11 of 22...
Installing ..\w61-x64\glb\WINDOWS6.1-KB981332-X64_2FD6C5B2BADC7BBEE4720082CE4FC1E4664ACBF2.CAB...
Installing update 12 of 22...
Installing ..\w61-x64\glb\WINDOWS6.1-KB978601-X64_05027175AB8FDF074B636ACFEBC0B1481B58B73A.CAB...
Installing update 13 of 22...
Installing ..\w61-x64\glb\WINDOWS6.1-KB980408-X64_877FA9E523B4241ADBCB437D932F416F183B7E66.CAB...
Installing update 14 of 22...
Installing ..\w61-x64\glb\WINDOWS6.1-KB978542-X64_2729AA5EE7DD850B989779CA6C325A3AF94CE8DB.CAB...
Installing update 15 of 22...
Installing ..\w61-x64\glb\WINDOWS6.1-KB981793-X64_A90E501036F9BB15424B80D1FE68227B85106278.CAB...
Installing update 16 of 22...
Installing ..\w61-x64\glb\WINDOWS6.1-KB980218-X64_E44A6FDAD2F4DB33D0288E50FD454243A3595ACF.CAB...
Installing update 17 of 22...
Installing ..\w61-x64\glb\WINDOWS6.1-KB979482-X64_8936A701FC7A868F988E37F3800BDE8BE231577F.CAB...
Installing update 18 of 22...
Installing ..\w61-x64\glb\WINDOWS6.1-KB979916-X64_240C3944A6B262DB596AF57BAD7807BF5DD6B8C6.CAB...
Installing update 19 of 22...
Installing ..\w61-x64\glb\WINDOWS6.1-KB980195-X64_516AA3C23A25638F3A935D07C2C10284F3413B85.CAB...
Installing update 20 of 22...
Installing ..\w61-x64\glb\WINDOWS6.1-KB979559-X64_30ED50ED48AF82DB9A77B014F46BDC6DDE06F557.CAB...
Installing update 21 of 22...
Installing ..\w61-x64\glb\WINDOWS6.1-KB982381-X64_ACCBFDC008E72B6B7405322FCA589208F577B58F.CAB...
Installing update 22 of 22...
Installing ..\w61-x64\glb\WINDOWS6.1-KB2032276-X64_7A81073CD18804A989DB2E214C588C2BC3CA9FB5.CAB...

Installation successful. Please reboot your system now.

[Gerby]

Hi icnocop!

Did you reboot the system before taking a look at the list of installed updates? (Just a guess, since I'm not familiar with Windows 7 or even the x64 version.)

Actually the DoUpdate.cmd script checks the user's privileges before going on, as you can see from the log. So it wouldn't run without elevated privileges.

Greetz
Gerby

[icnocop]

Thanks Gerby,

Yes, I did reboot before checking the list of installed updates.

But that should not matter because I noticed the updates show up while wsusoffline is running when invoked manually.

The event viewer did not have any pertinent information either.

Any other thoughts?

Thank you.

[icnocop]

Here is a sample c# windows console application that can reproduce this behavior.

The fix is to compile the application using the x64 configuration.
I am not sure why using x86 or "Any CPU" configurations failed to install updates and failed to report errors.

Any ideas?

I would rather not have to compile this application using the x64 configuration.

1. Run elevated C:\windows\system32\cmd.exe
2. RunCmd.exe "C:\WINDOWS_7_X64_UPDATES\CLIENT\CMD\DoUpdate.cmd" /nobackup

Thank you.

Code: Select all

using System;
using System.Diagnostics;

namespace RunCmd
{
    class Program
    {
        static void Main(string[] args)
        {
            try
            {
                string filename = args[0];
                string arguments = args[1];

                ProcessStartInfo _info = new ProcessStartInfo(filename, arguments);
                _info.RedirectStandardOutput = true;
                _info.UseShellExecute = false;
                _info.CreateNoWindow = true;

                Process _p = new Process();
                _p.StartInfo = _info;
                _p.Start();

                string _processResults = _p.StandardOutput.ReadToEnd();

                _p.Close();

                Console.WriteLine(_processResults);
            }
            catch (System.Exception e)
            {
                Console.WriteLine(e.ToString());
                Environment.Exit(1);
            }
        }
    }
}


[WSUSUpdateAdmin]

Hi!

I'm not sure what I should do with this.
If I got it right, everything works fine if you start DoUpdate.cmd from a privileged shell.
So why don't you use UpdateInstaller.exe? It does the required elevation request...

Regards
Torsten Wittrock

[icnocop]

Hi Torsten,

There is no problem installing updates manually (i.e. double-clicking on UpdateInstaller.exe or DoUpdate.cmd).

The problem is when I am trying to launch DoUpdate.cmd from a third party application so that it can automatically update the system without user intervention (silently \ unattended).

If the third party application is compiled using "Any CPU" or "x86" build configuration, then DoUpdate.cmd will not report any errors, but it will not perform any installations either, so it only appears successful when really it's not.

The only fix is to compile the third party application using the "x64" build configuration.

I would rather not have to compile the third party application using the "x64" build configuration, so I am wondering if there is any other way around this limitation?

I would have expected wsusoffline to at least report an error\failure.

Thank you.

[boco]

32bit programs don't have access to the Windows\System32 directory at all. All access gets redirected silently to Windows\SysWOW64. Somehow this seems to cause failure in your case. And I guess that 32bit programs can only start 32bit shells.

[icnocop]

Thank you boco,

I will try to disable registry redirection for my application and report back my findings.

[icnocop]

Registry redirection seems to only apply when dealing with handles\references to registry keys, so that is not applicable in the third party application.

So I tried to call Wow64DisableWow64FsRedirection to disable file system redirection and then tried launching
C:\WINDOWS\system32\cmd.exe /C C:\wsusoffline\client\Update.cmd /nobackup
and
C:\WINDOWS\SysWOW64\cmd.exe /C C:\wsusoffline\client\Update.cmd /nobackup
but neither command installed any updates.

I would have thought this approach would allow a 32-bit process (the third party application) to launch a 64-bit process (cmd.exe which is then used to run Update.cmd).

Any thoughts?

Thank you.

[boco]

Could you use a small 64bit wrapper/forwarder?