Darr247

With the subject "How to extract directx_feb2010_redist.exe manually to HFCABS" it would be nice, in my opinion, if it actually told how-to manually extract the DirectX 9.0c runtime cabs to the HFCABS subdir. Thanks.

So, how do we convert the old links like http://www.msfn.org/board/unattended-wireless-network-connection-t88734-pid-895875.html to the format the board uses now?

In the sticky thread of this same title, the first line is When WUD starts up, it loads all of the UL files from the directory where WUD resides in. I don't know when that changed, but it's not so... in XP they're loaded from: %userprofile%\Local Settings\Application Data\Supremus Corporation\Windows Update Downloader\ Hope that helps.

I agree. Currently the XP SP3 update list has 64 critical, 1 Service Pack, 4 WMP11, 2 UNIX services and 12 Other for 83 total in the XP SP3 UL available. However, I have done a fresh install of XP Pro SP3 IE 8 WMP 10 followed by WMP11 dotNET 1, 1.1, 3.5 SP1 (which includes 2.0, 3.0 and 3.5) and 4.0 Then manually downloaded all the updates listed when I click the 'yellow shield' and choose Custom. I count 115 files, with about 5 of them being 'optional' (KB updates to XP, plus root cert authority and time zone DST updates; NOT including the 'optional' Live or Search updates). A couple of the 'info' links for the updates end up pointing to the same KB file, but installing that file does not get rid of the yellow shield 'updates available' notice for either of those KB's, by the way. Anyway... since WUD won't accept the files I have already downloaded (I understand why, this solution just doesn't do what I want - to stop having to download 100+ updates every time I reinstall windows on our 3 desktops and 3 laptops... since WUD won't accept files I have already downloaded, I would still have to download them all again every time I use it), so I'm just going to dump them all in one subdirectory and run the echo hotfix post SP3... for %%a in (*.exe) do ( start /wait %%a /quiet /norestart /nobackup ) pause batch file suggested by -X- in another thread here, even though that means they'll be installed in alphabetical order instead of the order they're given in the Windows Update list.