This project has moved and is read-only. For the latest updates, please go here.

Strange error with Win2012 R2

Topics: Configuration Issue
May 7, 2014 at 6:51 PM
I'm encountering an error 0x80070643 / 0x80131700 with a package I've rolled out, which tries to unregister VGX.DLL. It worked on XP and Win7 (and 2003 and 2008), but not 2012. I'm not sure if it's some kind of bug or some permissions setting that I'm missing. Also there was no WPP log file created in C:\Windows\Temp.

Here's the log from one of our servers:

2014-05-07 04:35:05:364 884 b7c AU #############
2014-05-07 04:35:05:364 884 b7c AU ## START ## AU: Install updates
2014-05-07 04:35:05:364 884 b7c AU #########
2014-05-07 04:35:05:364 884 b7c AU # Initiating minor updates install
2014-05-07 04:35:05:364 884 b7c AU # Approved machine updates for 3DA21691-E39D-4DA6-8A4B-B43877BCB1B7 = 1
2014-05-07 04:35:05:364 884 b7c AU # Approved updates for 3DA21691-E39D-4DA6-8A4B-B43877BCB1B7 = 1
2014-05-07 04:35:05:364 884 b7c IdleTmr WU operation (CInstallCall::Init ID 3) started; operation # 25; does not use network; is not at background priority
2014-05-07 04:35:05:364 884 b7c IdleTmr Incremented PDC RefCount for System to 1
2014-05-07 04:35:05:364 884 b7c IdleTmr Incremented idle timer priority operation counter to 1
2014-05-07 04:35:05:364 884 b7c Agent Beginning install of conventional work item
2014-05-07 04:35:05:364 884 b7c AU <<## SUBMITTED ## AU: Install updates / installing updates [CallId = {B833BFAB-4534-4BCA-A9F8-25CBF0A55D23}, ServerId = {3DA21691-E39D-4DA6-8A4B-B43877BCB1B7}]
2014-05-07 04:35:05:364 884 aa4 Agent *************
2014-05-07 04:35:05:364 884 aa4 Agent ** START ** Agent: Installing updates [CallerId = AutomaticUpdates]
2014-05-07 04:35:05:364 884 aa4 Agent *********
2014-05-07 04:35:05:364 884 aa4 Agent * Updates to install = 1
2014-05-07 04:35:05:364 884 b7c AU WARNING: Failed to get Network Cost info from NLM, assuming network is NOT metered, error = 0x80240037
2014-05-07 04:35:05:364 884 b7c AU WARNING: Failed to get Network Cost info from NLM, assuming network is NOT metered, error = 0x80240037
2014-05-07 04:35:05:379 884 aa4 Agent * Title = VGX.DLL fix (Win8)
2014-05-07 04:35:05:379 884 aa4 Agent * UpdateId = {F09C3A72-94A7-46EF-A730-8D0DF9F0048A}.2
2014-05-07 04:35:05:395 884 aa4 DnldMgr Preparing update for install, updateId = {F09C3A72-94A7-46EF-A730-8D0DF9F0048A}.2.
2014-05-07 04:35:05:395 4088 3e0 Misc =========== Logging initialized (build: 7.9.9600.16422, tz: -0500) ===========
2014-05-07 04:35:05:395 4088 3e0 Misc = Process: C:\Windows\system32\wuauclt.exe
2014-05-07 04:35:05:395 4088 3e0 Misc = Module: C:\Windows\SYSTEM32\wuaueng.dll
2014-05-07 04:35:05:395 4088 3e0 Handler :::::::::::::
2014-05-07 04:35:05:395 4088 3e0 Handler :: START :: Handler: Command Line Install
2014-05-07 04:35:05:395 4088 3e0 Handler :::::::::
2014-05-07 04:35:05:395 4088 3e0 Handler : Updates to install = 1
2014-05-07 04:35:05:411 4088 3e0 Handler : WARNING: Command line install completed. Return code = 0x80131700, Result = Failed, Reboot required = false
2014-05-07 04:35:05:411 4088 3e0 Handler : WARNING: Exit code = 0x8024200B
2014-05-07 04:35:05:411 884 b7c AU >>## RESUMED ## AU: Installing update [UpdateId = {F09C3A72-94A7-46EF-A730-8D0DF9F0048A}]
2014-05-07 04:35:05:411 4088 3e0 Handler :::::::::
2014-05-07 04:35:05:411 884 b7c AU # WARNING: Install failed, error = 0x80070643 / 0x80131700
2014-05-07 04:35:05:411 4088 3e0 Handler :: END :: Handler: Command Line Install
2014-05-07 04:35:05:411 4088 3e0 Handler :::::::::::::
2014-05-07 04:35:05:411 884 aa4 Agent *********
2014-05-07 04:35:05:411 884 aa4 Agent ** END ** Agent: Installing updates [CallerId = AutomaticUpdates]
2014-05-07 04:35:05:411 884 aa4 Agent *************
May 8, 2014 at 6:48 AM
Hi,

the error 0x80240037 is reported in this KB: http://support.microsoft.com/kb/938205/de
0x80240037 WU_E_NOT_SUPPORTED The functionality for the operation is not supported.

Can you do the same manually? Is it working if you try it manually?
May 8, 2014 at 10:07 AM
Hi,
  • Do you have set a 'custom update' or a 'classic update' ?
    In case of a 'Custom update', please do this :
    Open WPP
    Select the update
    In the 'Informations' tab, click on the 'Id' link, this oopen a new window
    In the new window, open the folder and send me the file 'Guid.xml'
  • Do you have checked the option 'Can require user input' when making the update ?
May 8, 2014 at 4:37 PM
I've created a classic update based on a custom update (I've learned to reverse engineer it to avoid the GUI and long GUIDs). Also, no, the "can require user input" is not enabled. I've tried the package manually and it does work on Win7/2008R2, which leads me to think it's some new ACL with 2012. No real clue though. I've added the cert for the server and clients, enabled the registry key, as I have done for all other servers.

Here's what the vgx.xml I've created looks like:

<CustomUpdate>
<Action>
<ElementType>CustomUpdateElements.ExecutableElement</ElementType>
<PathToExecutable>regsvr32.exe</PathToExecutable>
<Parameters>/u /s "C:\Program Files (x86)\Common Files\Microsoft Shared\VGX\vgx.dll"</Parameters>
<KillProcess>True</KillProcess>
<TimeBeforeKilling>5</TimeBeforeKilling>
<Variable/>
</Action>
<Action>
<ElementType>CustomUpdateElements.ExecutableElement</ElementType>
<PathToExecutable>regsvr32.exe</PathToExecutable>
<Parameters>/u /s "C:\Program Files\Common Files\Microsoft Shared\VGX\vgx.dll"</Parameters>
<KillProcess>True</KillProcess>
<TimeBeforeKilling>5</TimeBeforeKilling>
<Variable/>
</Action>
</CustomUpdate>

I've bundled the 2012 version of regsvr32.exe to make sure that it should work. Same error whether I bundle the Win7/2008 or the 2012 version.
May 8, 2014 at 5:28 PM
I've created a classic update based on a custom update (I've learned to reverse engineer it to avoid the GUI and long GUIDs).
What do you mean ? How do you have make this package ?
When you revise the update, what is set in the command line ?

You should find a C:\Windows\Temp\CustomUpdateEngine.log. Can you copy the content here ?
May 8, 2014 at 6:50 PM
I create custom packages by mimicking how it works. I create a regular package calling C:\WSUS_PP\CustomUpdateEngine.exe, include my own action file (e.g. vgx.xml) and any other necessary files, then use the parameter "\actionfile=vgx.xml". I've done all my customizations this way. I only use the custom package GUI to figure out the necessary parameters for the XML file. The command line calls the CustomUpdateEngine.exe, as stated above.

That's the strange part. No customupdateengine.log file is created. On machines that the package worked on, it's there. On the Win2012 boxes, the log isn't there. Firewall port issues perhaps?
May 8, 2014 at 7:10 PM
That's the strange part. No customupdateengine.log file is created. On machines that the package worked on, it's there. On the Win2012 boxes, the log isn't there.
Then, customengine.exe don't run. Do you have .Net Framework 2.0 or 3.5 installed on the client machines ?
Marked as answer by DCourtel on 5/9/2014 at 12:14 PM
May 9, 2014 at 8:11 PM
Yes, thank you! That was the problem. Win2012 does not install .Net 3.5 by default. Glad to put this to bed before heading into the weekend. Cheers!