I now present to you, an Autopatcher Replacement


Recommended Posts

I’m Proud to announce an autopatcher replacement. The Process isn’t as automated as autopatcher, this is to say you can’t just download one big file and have all the updates. Though that same luxury is what got autopatcher spanked in the first place.

The new process will require you to create your own file, but once you do you can reuse the file on many newly installed XP machines.

This new process has to do with the windows softwaredistribution folder (C:\windows\softwaredistrubution). This is the location where windows stores the automatic updates before it installs them. This is what the process entails. First create a fresh install of XP (preferable in vmware) set automatic updates to “Download updates for me, but let me choose when to install them”. Then wait until all 82 updates have been downloaded but do not install them. You then copy the contents of the softwaredistribution folder to a desired location and create a self extracting zip of the folder called “xpupdates.exe” that automatically extracts to c:\windows\softwaredistrubution. Once done you can use that self extracting exe on any fresh install XP machines requiring updates.

So is this just like autopatcher, well no!. But it will take you less than a few mins to implement and save you alot of downloading time for windows XP updates. Installing all 82 updates on a machine with 256 megs of ram took all of 7 mins, in comparison to autopatcher that took 30 + mins

The process does require an internet connection just to say "hey what up" to the automatic update server, but then again if the computer didn't have an internet connection then the security updates wouldn't be that important anyway.

The updates being acquired are done so on machines that haven't even been activated let a lone validated, so these are updates any computer has access to, and you would not be bypassing WGA validation.

I’d recommend putting that file on a thumbstick or a cd. When you are ready to update an XP machine you are going perform the following tasks

1) Set the automatic update to “Download updates for me, but let me choose when to install them”

2) Stop the automatic update service via services.msc

3) Delete the contents of the software distribution folder

4) Extract xpupdates.exe

5) Turn automatic updates back on

6) Run a script which tells automatic updates to check for updates

Once windows checks for updates it will see there are updates available, but it will also see they are already on the machine, and will just prompt you to install them, without having to download anything.

Instead of having to complete the following tasks on a new machine, I’ve tried simplifying the process via a batch file. All that is required of you is that you have a file called xpupdates.exe on any mountable media with all the updates you with to apply.

Below is the batch file code

And the actual batch file

@echo off

cls

Echo Welcome to the Neowin.net XP softwaredistrubution updater

Echo This process will Stop the Automatic Update service, clear the softwaredstrubution folder, copy the new updates to the software distrubution folder, then restart the automatic update service and force automatic updates to check for updates

Echo When you are ready to begin

Pause

cls

echo Stopping the Automatic Update Service

net stop wuauserv

cls

echo deleting contents of the softwaredistrubution folder

rd C:\windows\SoftwareDistribution\authcabs /s /q

rd C:\windows\SoftwareDistribution\datastore /s /q

rd C:\windows\SoftwareDistribution\download /s /q

rd C:\windows\SoftwareDistribution\selfupdate /s /q

del C:\windows\SoftwareDistribution\ /q

cls

set /p drive=Please enter the drive letter where the updates are located (example d:) :

%drive%\updates\xpupdates.exe

cls

net start wuauserv

wuauclt /detectnow

@echo off

Echo This AU client will now check for the Updates on the Local WSUS Server.

Pause

The batch file will be presented as Neowin.net if that works for all of you?

the batch file has not been thoroughly tested, so I need you guys to help me test it, and if you want to add new things to it, please post your ideas in this thread, and together we can make a really great autopatcher replacement.

also any idiots out there that feel it their duity to rate this thread a 1 star, please leave a comment and share your opinions

Here is a video explaining how this process works http://www.vidilife.com/index.cfm?f=media....9C6-47FB-8503-C

autoupdate.zip

Edited by warwagon

ya I pretty much suck at coding, i'm surprised I even got it working thus far. So if anyone could write some code that could detect if the file isn't there and restart the service and just exit

First portion of the VBS code is this:

Const wshYes = 6
Const wshNo = 7
Const wshYesNo = 4
Const wshinformation = 64
Const wshOkOnly = 0

Set objShell = CreateObject("Wscript.Shell")

Start=objShell.Popup("Welcome to the Neowin.net XP software distrubution updater. This Program makes changes to the Windows Update System. Do you wish to continue?", 10, "Auto Update by Warwagon", wshYesNo+wshInformation)

If Start = wshNo Then

Wscript.Quit

Else If Start = wshYes Then

Start=objShell.Popup("Stopping Windows Update Service, Please wait...", 01, "Auto Update by Warwagon", wshOKOnly+wshInformation)
objShell.Run ("net stop wuauserv"),,True

Start=objShell.Popup("Deleting contents of Software distribution folder, Please wait...", 01, "Auto Update by Warwagon", wshOKOnly+wshInformation)
objShell.Run ("cmd /c rd C:\windows\SoftwareDistribution\authcabs /s /q"),,True
objShell.Run ("cmd /c rd C:\windows\SoftwareDistribution\datastore /s /q"),,True
objShell.Run ("cmd /c rd C:\windows\SoftwareDistribution\download /s /q"),,True
objShell.Run ("cmd /c rd C:\windows\SoftwareDistribution\selfupdate /s /q"),,True
objShell.Run ("cmd /c del C:\windows\SoftwareDistribution\ /q"),,True

Wscript.quit

End If
End If

If i get time i will write the rest of the code soon for you.

OK, i have updated the version from above, because it had an error if the file was not on the drive you specified.

The new script will allow the user to enter the full location of any file name, so instead of looking specifically for xpupdates.exe, you could call it teh_haxord_updates.exe and so long as you point it to that file, it will run it.

If it does not find the file you specified, it will give you an error and allow you to specify the location again. You have 3 tries, after which you will need to re-run the script in order to try again.

You can run the script on any version of windows that has windows updates on it that allows scripts to run.

Please let me know if you find any errors or have any change requests with the script and i will be pleased to help.

Point of note: use the environment variable %WINDIR% to get around "Windows not installed on C:" difficulties (right-click My Computer --> Properties: Advanced tab --> Environment Variables button to see your own). Installations don't have to be on C:, or even in a directory called "windows".

You could even use %COMSPEC% to get an absolute path to cmd.exe...

Point of note: use the environment variable %WINDIR% to get around "Windows not installed on C:" difficulties (right-click My Computer --> Properties: Advanced tab --> Environment Variables button to see your own). Installations don't have to be on C:, or even in a directory called "windows".

You could even use %COMSPEC% to get an absolute path to cmd.exe...

That is a good point mate. I never thought of that.

Ill correct it and upload an updated version.

Its only a simple script mate. Not a lot to close really. Anyone with a little knowledge of windows scripting could make this.

Well you didn't, so give the author his credit. Nice work on being another garden variety jackass in Neowin.

Well you didn't, so give the author his credit. Nice work on being another garden variety jackass in Neowin.

Actually i did.

Of course you ran the script before making that comment about me, right? ;) As you made yourself look foolish with the comment, ill let it slip and not report you for directly insulting a fellow member this time ;)

He did actually,

Cheers for backing me up there mate. :)

I am assuming you are talking about yourself

Lol. Quite :rofl:

Here is an update version which points to %windir% instead of C:\. Should sort out a few issues with the script :)

This one is not encrypted. I dont see the point now seeing as scripts are so easy to decrypt and there is no big secret in the scripting :)

Good work Rich

If even 1 person finds this method helpful then it'll be all worth it

Yep.

If people could download, try and present their feedback that would be cool. I'm looking to make it more friendly, by adding a feature which will download the updates from Windows Update, compile them to a ZIP or EXE file and will do all the necessary as well.

I'm then looking to convert all the information to VB (when i learn how ;)). So it will be an executable

Yep.

If people could download, try and present their feedback that would be cool. I'm looking to make it more friendly, by adding a feature which will download the updates from Windows Update, compile them to a ZIP or EXE file and will do all the necessary as well.

I'm then looking to convert all the information to VB (when i learn how ;)). So it will be an executable

ya there are a bunch of good programmers on this site, if only a 1 of them would take your wonderful script and turn it into VB

This topic is now closed to further replies.
  • Recently Browsing   0 members

    • No registered users viewing this page.
  • Posts

    • If I ever get that issue I will let you know how I fix it
    • As I've been usually saying lately - we all can thank "AI" for this.
    • Friday Windows 11 preview builds are here. Insiders in the Experimental (formerly Dev) and Beta Channel can download builds 26300.8697 and 26220.8690. My Windows11 device on the Preview Channel just got 26220.8728. My guess is this build is a nightly update from 26220.8690.
    • Traffic has a surprisingly unexpected impact on your surroundings by Sayan Sen Image by Radik 2707 via Pexels A collaborative study by researchers from several Israeli institutions found that everyday pollution from traffic and industrial activity measurably changed the atmospheric electric field over the Tel Aviv metropolitan area, providing new evidence of how human activity can influence the lower atmosphere. The research was led by Dr. Roy Yaniv of the Hebrew University of Jerusalem and the Gertner Institute at Sheba Medical Center, Dr. Assaf Hochman of the Fredy & Nadine Herrmann Institute of Earth Sciences at the Hebrew University, and Prof. Yoav Yair of Reichman University. The study also involved Itay Froomer, a student from Hadera High School and the Israeli Museum of Medicine and Science (Technoda), who carried out the work as part of the Ministry of Education's 5-unit physics research track. The researchers focused on the atmospheric electric field under fair-weather conditions. Even in the absence of storms, a weak electric field naturally exists between Earth's surface and the atmosphere. One of the main ways scientists measure this field is through the Potential Gradient (PG), which is the inverse of the vertical component of the electric field. PG is a key part of the global electric circuit, a planet-wide system of electrical currents maintained by thunderstorms and electrified clouds around the world. Scientists have long known that the atmospheric electric field can be influenced by factors ranging from large-scale atmospheric processes to local weather conditions such as dust, fog and clouds. Human-made pollution is also known to play a role, but understanding exactly how urban emissions affect the electric field close to the ground has remained an area of ongoing research. To investigate this relationship, the team analyzed measurements from a newly installed electric field mill, an instrument used to continuously monitor the strength of the atmospheric electric field. The instrument was installed at the Center for Technological Education (Roter House) in Holon and became operational in August 2024. It was funded by Israel's Ministry of Education and the Holon municipality. The electric field mill forms part of a broader monitoring network that includes nearby meteorological stations and air-quality monitoring sites. This allowed researchers to compare electric field measurements with detailed weather data and pollution records to better understand what was driving changes in the Potential Gradient. The study focused on two major urban pollutants: fine particulate matter (PM2.5) and nitrogen oxides (NOx), both commonly produced by vehicle traffic and industrial activity. PM2.5 refers to microscopic airborne particles small enough to remain suspended in the atmosphere for extended periods, while NOx is a group of gases released during fuel combustion. Researchers examined daily, weekly and seasonal patterns in the atmospheric electric field and compared them with changes in pollutant concentrations. Their analysis revealed a clear relationship between NOx levels and changes in the Potential Gradient, particularly during morning and evening rush hours when traffic emissions were at their highest. “What we observe is a direct physical link between emission peaks and electrical variability,” explained Dr. Roy Yaniv. “NOx reduces atmospheric conductivity very quickly, so the electric field responds almost instantaneously during traffic rush hours.” Atmospheric conductivity describes how easily electrical charges move through the air. According to the researchers, nitrogen oxides rapidly alter this conductivity, causing a near-immediate response in the electric field. PM2.5, however, was associated with a delayed response. The researchers attributed this difference to the particles' longer atmospheric residence time, meaning they remain in the atmosphere for longer periods, as well as their different microphysical interactions with surrounding air and atmospheric components. The study also identified a pronounced "weekend effect." In Israel, traffic volumes and some industrial activity decline significantly on Fridays and Saturdays. During these periods, concentrations of both NOx and PM2.5 dropped, and corresponding changes were observed in the atmospheric electric field. “The weekend signal demonstrates just how sensitive the electric field is to changes in human activity,” the researchers noted. “When emissions decline, the electrical environment adjusts at once, providing a high-resolution indicator of urban atmospheric conditions.” The findings showed that pollution levels can influence not only the chemical composition of the atmosphere but also its electrical properties. Researchers said the results strengthened the case for using atmospheric electricity as an additional tool for environmental monitoring, particularly in densely populated urban areas where anthropogenic, or human-caused, influences are most pronounced. The study also pointed to potential public health applications. By combining air-quality measurements with observations of atmospheric electricity, researchers said they could gain a more complete picture of how urban atmospheric conditions change over time. “Integrating air-quality data with electric-field measurements gives us a clearer picture of how the lower atmosphere evolves moment by moment,” the researchers added. “It’s a framework that can support both scientific insight and practical environmental decision-making.” Beyond the scientific findings, the project highlighted a collaboration between universities, public institutions and secondary education. Researchers said the work demonstrated how students could take part in real-world environmental research while contributing to studies of air quality, atmospheric processes and their potential effects on society. Source: Hebrew University, ScienceDirect This article was generated with some help from AI and reviewed by an editor. Under Section 107 of the Copyright Act 1976, this material is used for the purpose of news reporting. Fair use is a use permitted by copyright statute that might otherwise be infringing
  • Recent Achievements

    • Week One Done
      AMV earned a badge
      Week One Done
    • One Month Later
      AMV earned a badge
      One Month Later
    • Collaborator
      ryansurfer98 went up a rank
      Collaborator
    • One Month Later
      Eurosoft10 earned a badge
      One Month Later
    • Week One Done
      Eurosoft10 earned a badge
      Week One Done
  • Popular Contributors

    1. 1
      +primortal
      540
    2. 2
      +Edouard
      186
    3. 3
      PsYcHoKiLLa
      80
    4. 4
      Michael Scrip
      77
    5. 5
      Steven P.
      72
  • Tell a friend

    Love Neowin? Tell a friend!