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

[Solved] Custom Update XML-File

Topics: Configuration Issue
Jun 5, 2014 at 9:50 AM
After creating a custom update, no customupdateengine.exe is pre-filled, and no customupdate xml-file was build.

WPP 1.3.1405.17, Server 2003 and WSUS 3.2.7600.226

what's wrong here ??
Jun 5, 2014 at 11:02 AM
I can't get this issue to happen on my computer (even with the same version of WPP).
Is it the first installation or, do you have a previous installation and then upgrade to 1.3.1405.17 ?
Does it have already works ?
Jun 5, 2014 at 11:18 AM
Yes, it works the first time with a previous installation.
I think the sixth installation has failed with the previous installation, and also with the upgrade.
Jun 5, 2014 at 8:28 PM
can you try to reproduce the bug and then go to %temp% and search for the file WPP-Guid.log. Send it to me at package.publisher@free.fr
Jun 6, 2014 at 8:18 PM
I can concur with Thomas on that, see below at hte bottom of this post. I stopped after getting past adding files. The next screen "Creation window" I see the command line field is filled out with the action file switch and the file but the previous screen is not autofilled out.

Thomas: I know that I can successfully get the customupdateengine.exe & it's action file filled if I use it from the WSUS server, but not using my workstation. Perhaps we need to purge our %temp% before running this latest version?

I sent you the file DCourtel.
Jun 6, 2014 at 10:50 PM
Can you check if 'CustomUpdateEngine.exe' if present in the same directory than 'Wsus Package Publisher.exe'
Jun 9, 2014 at 1:58 PM
Edited Jun 9, 2014 at 2:06 PM
It's sitting in the same folder:
05/23/2014  01:42 PM    <DIR>          .
05/23/2014  01:42 PM    <DIR>          ..
08/25/2013  03:29 PM           478,664 Catalogs' subscriptions management.pdf
11/10/2013  10:52 PM            25,088 CheckComboBox.dll
10/01/2012  08:35 PM           253,969 Creating a Code Signing Certificate.pdf
11/02/2013  11:58 AM           793,049 Custom Updates.pdf
05/17/2014  10:01 PM           142,336 CustomUpdateCreator.exe
05/17/2014  10:00 PM           374,784 CustomUpdateElements.dll
05/17/2014  10:01 PM             7,680 CustomUpdateElementViewer.dll
05/17/2014  10:00 PM            50,176 CustomUpdateEngine.exe
10/16/2013  10:06 PM    <DIR>          de
10/16/2013  10:06 PM    <DIR>          en
11/02/2013  03:45 PM    <DIR>          Exported Packages
10/18/2013  09:05 PM    <DIR>          fr
08/25/2013  03:27 PM           368,184 Importing Updates from Vendor's Catalog.pdf
10/10/2013  08:56 PM           769,629 Installation Guide.pdf
05/17/2014  10:00 PM            14,336 InstallPendingUpdates.exe
09/01/2013  08:21 PM            86,016 Interop.WUApiLib.dll
08/09/2013  02:48 PM            49,152 Microsoft.Deployment.Compression.Cab.dll
08/09/2013  02:48 PM            36,864 Microsoft.Deployment.Compression.dll
05/12/2013  05:51 PM            11,776 MsiReader.dll
12/02/2013  11:58 AM               416 Options.xml
09/01/2013  08:21 PM            23,040 ProductKiller.exe
05/23/2014  01:42 PM    <DIR>          ru
12/05/2013  12:12 AM    <DIR>          Rules
12/23/2013  12:33 AM    <DIR>          Saved Rules
08/25/2013  06:38 PM    <DIR>          Shared Catalogs
05/17/2014  10:01 PM           404,992 ShowPendingUpdates.exe
12/23/2013  12:34 AM    <DIR>          Subscribed Catalogs
12/05/2013  12:17 AM               753 Wsus Package Publisher Certificate.cer
05/17/2014  10:01 PM         4,823,040 Wsus Package Publisher.exe
12/02/2013  01:28 PM             2,907 Wsus Package Publisher.lnk
              21 File(s)      8,716,851 bytes
              11 Dir(s)  89,256,792,064 bytes free
Jun 9, 2014 at 4:19 PM
Can you right click on the file and choose "Properties". Then, in the General Tab, look at the bottom to see if there is a warning such as "This file came from another computer and might be blocked to help protect this computer".
Jun 9, 2014 at 5:03 PM
Checking out the CustomUpdateCreator.exe has no warning "This file came from another computer and might be blocked to help protect this computer".
Jun 10, 2014 at 1:29 PM
"This file came from another computer and might be blocked to help protect this computer"
This was the failure - thank you !
Marked as answer by DCourtel on 6/11/2014 at 11:04 AM
Jun 10, 2014 at 8:59 PM
Checking out the CustomUpdateCreator.exe has no warning
Please, check CustomUpdateEngine instead of CustomUpdateCreator.

I have sent you a release of WPP with more logging around this function.
What is the full path of 'CustomUpdateEngine.exe' ?
Jun 11, 2014 at 7:04 PM
Thanks for your feed back.
Effectively, using C:\Windows\System32\hstart.exe to start WPP as a parameter is a scenario that I didn't expected.

Good to know.
Marked as answer by DCourtel on 6/11/2014 at 11:04 AM