Update catalog will be replaced by Windows Hotfix Downloader. Alphawaves has given me permission to use his update lists. I will start programming this after my Tuesday exam

Greate news, thanks to alphawaves and the update list maintainers

Yeah, great news!!! Also like to thank all the members involved in WHD, especially Alphawaves and abbodi1406!!!

YEAH! Long life Alphawaves & Co!

Hi!

Can't open Windows Hotfix Downloader.

It says Out of memory, how much does it need?

I have a quad core x64 comp. with 4gb ram and Win7.

Any suggestions?

Falo, Windows Hotfix Downloader is not in WinToolkit yet? The only thing in it is opening a link to its website :/

Just wanted to bump this a little. I updated my archives (as you can see here and here), but I won't keep updating them in the future as WHD does a great job and my work seems a little redundant.

 

So please Lego, hope you'll finish integrating the update lists, so Win Toolkit can download directly the needed updates, and this before ~ 15 of february. So all users can enjoy patch tuesday updates / hotfixes from next month

Yes I know it's not inside Wintoolkit.

I downloaded it and tried to use it, unfortunally I get a Unhandled exception always when I start it up.

I have .win7 x64, net 4.5.1, 4gb ram, 130gb free on d: and 93gb free on c:

I have cleared the temp, tested to move it from d: to c:, reinstalled .net.

I can see that people use it to download updates (not me then).

Do I need some files that is missing or does it need more than 4gb ram which sounds strange.

Here are the details from the "Unhandled exception" :

 

************** Exception Text **************
System.OutOfMemoryException: Insufficient memory to continue the execution of the program.
   at System.Management.ManagementScope.Initialize()
   at System.Management.ManagementEventWatcher.Initialize()
   at System.Management.ManagementEventWatcher.Start()
   at WindowsHotfixDownloader.SolutionHelper.TestRegistry(Object , RunWorkerCompletedEventArgs )


************** Loaded Assemblies **************
mscorlib
    Assembly Version: 4.0.0.0
    Win32 Version: 4.0.30319.18408 built by: FX451RTMGREL
    CodeBase: file:///C:/Windows/Microsoft.NET/Framework64/v4.0.30319/mscorlib.dll
----------------------------------------
WindowsHotfixDownloader
    Assembly Version: 5.0.0.4
    Win32 Version: 5.0.0.4
    CodeBase: file:///D:/Winfix/win7orig/WindowsHotfixDownloader.exe
----------------------------------------
System
    Assembly Version: 4.0.0.0
    Win32 Version: 4.0.30319.18408 built by: FX451RTMGREL
    CodeBase: file:///C:/Windows/Microsoft.Net/assembly/GAC_MSIL/System/v4.0_4.0.0.0__b77a5c561934e089/System.dll
----------------------------------------
WindowsHotfixDownloader&
    Assembly Version: 1.0.0.0
    Win32 Version: 5.0.0.4
    CodeBase: file:///D:/Winfix/win7orig/WindowsHotfixDownloader.exe
----------------------------------------
System.Windows.Forms
    Assembly Version: 4.0.0.0
    Win32 Version: 4.0.30319.18408 built by: FX451RTMGREL
    CodeBase: file:///C:/Windows/Microsoft.Net/assembly/GAC_MSIL/System.Windows.Forms/v4.0_4.0.0.0__b77a5c561934e089/System.Windows.Forms.dll
----------------------------------------
System.Drawing
    Assembly Version: 4.0.0.0
    Win32 Version: 4.0.30319.18408 built by: FX451RTMGREL
    CodeBase: file:///C:/Windows/Microsoft.Net/assembly/GAC_MSIL/System.Drawing/v4.0_4.0.0.0__b03f5f7f11d50a3a/System.Drawing.dll
----------------------------------------
System.Management
    Assembly Version: 4.0.0.0
    Win32 Version: 4.0.30319.18408 built by: FX451RTMGREL
    CodeBase: file:///C:/Windows/Microsoft.Net/assembly/GAC_MSIL/System.Management/v4.0_4.0.0.0__b03f5f7f11d50a3a/System.Management.dll
----------------------------------------
System.Configuration
    Assembly Version: 4.0.0.0
    Win32 Version: 4.0.30319.18408 built by: FX451RTMGREL
    CodeBase: file:///C:/Windows/Microsoft.Net/assembly/GAC_MSIL/System.Configuration/v4.0_4.0.0.0__b03f5f7f11d50a3a/System.Configuration.dll
----------------------------------------
System.Xml
    Assembly Version: 4.0.0.0
    Win32 Version: 4.0.30319.18408 built by: FX451RTMGREL
    CodeBase: file:///C:/Windows/Microsoft.Net/assembly/GAC_MSIL/System.Xml/v4.0_4.0.0.0__b77a5c561934e089/System.Xml.dll
----------------------------------------
System.Core
    Assembly Version: 4.0.0.0
    Win32 Version: 4.0.30319.18408 built by: FX451RTMGREL
    CodeBase: file:///C:/Windows/Microsoft.Net/assembly/GAC_MSIL/System.Core/v4.0_4.0.0.0__b77a5c561934e089/System.Core.dll
----------------------------------------

************** JIT Debugging **************
To enable just-in-time (JIT) debugging, the .config file for this
application or computer (machine.config) must have the
jitDebugging value set in the system.windows.forms section.
The application must also be compiled with debugging
enabled.

For example:

<configuration>
    <system.windows.forms jitDebugging="true" />
</configuration>

When JIT debugging is enabled, any unhandled exception
will be sent to the JIT debugger registered on the computer
rather than be handled by this dialog box.


Does anyone have a clue?

In the meantime I have downloaded RicaNeagas updatepacks (Thanks by the way)

 

/Falo

If I'm honest, I have no idea and I have nothing to do with that program what-so-ever. Definitely seems to be a memory leak though.

Im so happy about this integration.

WHD is also a great tool and going the same way of WTK.

 

Few questions:

- Would it will be a full integration?

Means, supported the full (main)-functionality;

Example: Can also delete superseded updates?

- Whats about the update-structur of code?

Means, if comes updates for WHD, comes also for WTK?

- Whats about integrate .UL list?

Or can i convert UL into .xml and "hard" integrate?

(My dream would be a mega updatelist, thats the result of work of all update-Repo makers.

Or for alternative i can adding xmls from all repo maker, so i can choice what i want download.)

I don't think a full integrate will be the best choice and frankly who would ever want that?

 

I was thinking that WTK will have acces to the updates repo of WHD and after some time of lacking it it finally have an built in updates downloader. That's all it needs in my opinion from WHD.

 

Who wants the other features of WHD, just use it as separate program.

I've currently got it to the point where you can actually download updates, etc.. At the moment it looks exactly like the old Update Catalogue.

 

It will only use the same update lists. That's all.

Great news, I definitely prefer your GUI!

Oh.. mh.. Okay.
Was thinking that.

But then its not a "replacing", its "just" an updated existing update-catalog feature.
I would miss some functions, and i think some of them would be usefull also for existing update-catalog.
Example this "delete superseds" or this selecting-menus in newer versions, filter-options, and more...

(Im not meaning the other [same] stuff like convert msp etc, im just meaning the update-downloader-frame)

Yay, at the end its a thing of taste - may.
But no good news for me..

 

Update:

Or i do not right remember?

Have WTK original Update-Catalog for example this "right-click-on-list"-feature from WHD?

Edited January 28, 201411 yr by BrokenZer0

As I remember it the update catalog worked better than current WHD implementation.

 

For ex:

 

1. The new updates were auto-selected and presented on top of the list

 

2. All supersedded updates that are not in the curent list were moved to "Old" folder

 

That's what I still remember and wish they remain the same.

Okay thats sound good.

May i make request-post then for "mark all additional" example and still keep as wish.

 

But lets see whats the final implementation result, we waiting for Lego.

@BrokenZero, 
 
As ianymaty said, new updates should be auto-selected. If an update is superseded, then why on earth would you want to keep it anyway?  Having it moved to the "Old" folder is best, IMHO.  You will still have it available if you ever need to use it at a later time, but Win Toolkit would not integrate it anyway, AFAIK, so that seems the best approach.  Or did I misunderstand what you meant by "mark all additional".
 
Cheers and Regards

@bphlpt
Unfortunately yes, you did misunderstand.
My mistake, may i have to really proof my english texting.

Yea, in first i was thinking that no option for unselect/delete superseds exist in Update-Catalog-Tool (UCT).
Then ianymaty have tell me correct that UCT have already this option.
So i told that i may make a request - for other - things.

For example, this "mark all additionals"-feature.
Additionals means all extra downloads, like "Additional Updates" or "Extra Updates" from WHD Update list.

Everything that's in the repo will be downloadable through update catalog, don't worry.