svchost and Windows Update Solution

The two Microsoft Updates noted in earlier posts work great. I've added a
batch file to stop the services and delete the softwaredistribution folder.

(for 32-Bit Machines - others use the Windows Update Agent for your machine)

Download Windows Update Agent 3.0
http://download.windowsupdate.com/v7...gent30-x86.exe

Download Windows Update KB927891
http://www.microsoft.com/downloads/d...displaylang=en

Create a batch file
---------------------------------------------------------------------------------------
@echo off

net stop "Automatic Updates"
net stop "Background Intelligent Transfer Service"

RD c:\windows\softwaredistribution /s /
---------------------------------------------------------------------------------------

1. Run the Batch File
2. Run the Update Agent 3.0 Installer
3. Run the Windows Update KB927891
4. Reboot

That's It. No messing arount with disabling/enabling services. Try it.

Your batch file will delete the update history for Microsoft Update. Is
there a reason you feel that is needed?

John


"Bill Barrett - GatorPC" wrote:


> Create a batch file:
> ---------------------------------------------------------------------------------------
> @echo off
>
> net stop "Automatic Updates"
> net stop "Background Intelligent Transfer Service"
>
> RD c:\windows\softwaredistribution /s /q
> ---------------------------------------------------------------------------------------

The update history viewable on MU/WU is stored in DataStore.edb which
can become corrupted/fragmented due to scanning by antivirus software.
There is another update history stored in ReportingEvents.log located in
%windir%\SoftwareDistribution.

The detection scan hits DataStore.edb causing a buffer overflow.
One can run esentutl from a Command Prompt to defragment DataStore.edb
instead of deleting it in hopes that will resolve the issue -

esentutl /d %windir%\SoftwareDistribution\Datastore\datastore. edb

If that doesn't resolve the issue, attempt to Recover the file -

esentutl /r %windir%\SoftwareDistribution\Datastore\datastore. edb

[This command performs recovery, bringing all databases to a
consistent state]

The next to last resort is to attempt to Repair it -

esentutl /p %windir%\SoftwareDistribution\Datastore\datastore. edb

NOTE: MS recommends that if the system is imaged regularly that a new
system image be done after running ANY of the above operations

* On XP Home Edition, one must stop the Automatic Updates service PRIOR
to running the above. This wasn't the case when doing so on XP Pro *

The *last resort* is to delete DataStore.edb

To mitigate log/database corruption, MS suggests this:

Virus scanning recommendations for computers that are running Windows
Server 2003, Windows 2000, or Windows XP
http://support.microsoft.com/kb/822158
Last Review :October 30, 2006

For computers that are running Windows Server 2003, Windows 2000, or
Windows XP

Do not scan the following files and folders. These files are not at risk
of infection. If you scan these files, serious performance problems may
occur because of file locking.
Where a specific set of files is identified by name, exclude only
those files instead of the whole folder. Sometimes, the whole folder
must be excluded. Do not exclude any one of these based on the file name
extension. For example, do not exclude all files that have a .dit
extension. Microsoft has no control over other files that may use the
same extensions as the following files.

• Microsoft Windows Update or Automatic Update related files
• The Windows Update or Automatic Update database file. This file
is located in the following folder:
%windir%\SoftwareDistribution\Datastore

Exclude the Datastore.edb file.

• The transaction log files. These files are located in the
following folder:
%windir%\SoftwareDistribution\Datastore\Logs
Exclude the following files:
• Edb*.log

Note The wildcard character indicates that there may be several files.
• Res1.log
• Res2.log
• Edb.chk
• Tmp.edb

MowGreen [MVP 2003-2007]
===============
*-343-* FDNY
Never Forgotten
===============


vpc5fan wrote:

> Your batch file will delete the update history for Microsoft Update. Is
> there a reason you feel that is needed?
>
> John
>
>
> "Bill Barrett - GatorPC" wrote:
>
>
>
>>Create a batch file:
>>---------------------------------------------------------------------------------------
>>@echo off
>>
>>net stop "Automatic Updates"
>>net stop "Background Intelligent Transfer Service"
>>
>>RD c:\windows\softwaredistribution /s /q
>>---------------------------------------------------------------------------------------
>
>

MowGreen,

That looks like some good info. Do any services have to be stopped prior to
running the esentutl command with the switches you mentioned?

Those commands you mentioned may be needed for the following:

I have at least one machine that has had the latest KB927891 patch and
Windows Update Agent 3.0 installed and it no longer pegs my CPU however it
did still takes a longer than usual time "scanning" on Microsoft Update. It
may have been because I had reverted back to using Windows Update and Office
Update (have Office 2003) months ago until the working solution for this
issue came out. It did however find this months Windows and Office updates
and installed them just fine. I haven't decided whether to manually update
via Microsoft Update for a month or two just to make sure the svchost.exe
issue is fully resolved or just let AU press on and see what happens. I
figure I will have to manually update in order to see if I can fix the "long
scan time" issue.


John

"MowGreen [MVP]" wrote:

> The update history viewable on MU/WU is stored in DataStore.edb which
> can become corrupted/fragmented due to scanning by antivirus software.
> There is another update history stored in ReportingEvents.log located in
> %windir%\SoftwareDistribution.
>
> The detection scan hits DataStore.edb causing a buffer overflow.
> One can run esentutl from a Command Prompt to defragment DataStore.edb
> instead of deleting it in hopes that will resolve the issue -
>
> esentutl /d %windir%\SoftwareDistribution\Datastore\datastore. edb
>
> If that doesn't resolve the issue, attempt to Recover the file -
>
> esentutl /r %windir%\SoftwareDistribution\Datastore\datastore. edb
>
> [This command performs recovery, bringing all databases to a
> consistent state]
>
> The next to last resort is to attempt to Repair it -
>
> esentutl /p %windir%\SoftwareDistribution\Datastore\datastore. edb
>
> NOTE: MS recommends that if the system is imaged regularly that a new
> system image be done after running ANY of the above operations
>
> * On XP Home Edition, one must stop the Automatic Updates service PRIOR
> to running the above. This wasn't the case when doing so on XP Pro *
>
> The *last resort* is to delete DataStore.edb
>
> To mitigate log/database corruption, MS suggests this:
>
> Virus scanning recommendations for computers that are running Windows
> Server 2003, Windows 2000, or Windows XP
> http://support.microsoft.com/kb/822158
> Last Review :October 30, 2006
>
> For computers that are running Windows Server 2003, Windows 2000, or
> Windows XP
>
> Do not scan the following files and folders. These files are not at risk
> of infection. If you scan these files, serious performance problems may
> occur because of file locking.
> Where a specific set of files is identified by name, exclude only
> those files instead of the whole folder. Sometimes, the whole folder
> must be excluded. Do not exclude any one of these based on the file name
> extension. For example, do not exclude all files that have a .dit
> extension. Microsoft has no control over other files that may use the
> same extensions as the following files.
>
> • Microsoft Windows Update or Automatic Update related files
> • The Windows Update or Automatic Update database file. This file
> is located in the following folder:
> %windir%\SoftwareDistribution\Datastore
>
> Exclude the Datastore.edb file.
>
> • The transaction log files. These files are located in the
> following folder:
> %windir%\SoftwareDistribution\Datastore\Logs
> Exclude the following files:
> • Edb*.log
>
> Note The wildcard character indicates that there may be several files.
> • Res1.log
> • Res2.log
> • Edb.chk
> • Tmp.edb
>
> MowGreen [MVP 2003-2007]
> ===============
> *-343-* FDNY
> Never Forgotten
> ===============
>
>
> vpc5fan wrote:
>
> > Your batch file will delete the update history for Microsoft Update. Is
> > there a reason you feel that is needed?
> >
> > John
> >
> >
> > "Bill Barrett - GatorPC" wrote:
> >
> >
> >
> >>Create a batch file:
> >>---------------------------------------------------------------------------------------
> >>@echo off
> >>
> >>net stop "Automatic Updates"
> >>net stop "Background Intelligent Transfer Service"
> >>
> >>RD c:\windows\softwaredistribution /s /q
> >>---------------------------------------------------------------------------------------
> >
> >
>

> * On XP Home Edition, one must stop the Automatic Updates service PRIOR
> to running the above. This wasn't the case when doing so on XP Pro *

The above was my finding on running esentutl. I ran the defrag command
and it made a noticeable difference on a VPC install of XP HE.
However, Office is not installed and the detection scan was done at
Windows Update.

The changes at WU/MS update include a new MSO.dll combined with the
latest Windows Update Agent, and a newer version of msi.dll [KB927891].

The changes *should* make a noticeable difference when scanning at MU,
but if the database has already been damaged ... then it may not
completely alleviate the issue.
Give the defrag command a try and see if it helps any.

MowGreen [MVP 2003-2007]
===============
*-343-* FDNY
Never Forgotten
===============



vpc5fan wrote:
> MowGreen,
>
> That looks like some good info. Do any services have to be stopped prior to
> running the esentutl command with the switches you mentioned?
>
> Those commands you mentioned may be needed for the following:
>
> I have at least one machine that has had the latest KB927891 patch and
> Windows Update Agent 3.0 installed and it no longer pegs my CPU however it
> did still takes a longer than usual time "scanning" on Microsoft Update. It
> may have been because I had reverted back to using Windows Update and Office
> Update (have Office 2003) months ago until the working solution for this
> issue came out. It did however find this months Windows and Office updates
> and installed them just fine. I haven't decided whether to manually update
> via Microsoft Update for a month or two just to make sure the svchost.exe
> issue is fully resolved or just let AU press on and see what happens. I
> figure I will have to manually update in order to see if I can fix the "long
> scan time" issue.
>
>
> John
>
> "MowGreen [MVP]" wrote:
>
>
>>The update history viewable on MU/WU is stored in DataStore.edb which
>>can become corrupted/fragmented due to scanning by antivirus software.
>>There is another update history stored in ReportingEvents.log located in
>>%windir%\SoftwareDistribution.
>>
>>The detection scan hits DataStore.edb causing a buffer overflow.
>>One can run esentutl from a Command Prompt to defragment DataStore.edb
>>instead of deleting it in hopes that will resolve the issue -
>>
>>esentutl /d %windir%\SoftwareDistribution\Datastore\datastore. edb
>>
>>If that doesn't resolve the issue, attempt to Recover the file -
>>
>>esentutl /r %windir%\SoftwareDistribution\Datastore\datastore. edb
>>
>>[This command performs recovery, bringing all databases to a
>>consistent state]
>>
>>The next to last resort is to attempt to Repair it -
>>
>>esentutl /p %windir%\SoftwareDistribution\Datastore\datastore. edb
>>
>>NOTE: MS recommends that if the system is imaged regularly that a new
>>system image be done after running ANY of the above operations
>>
>>* On XP Home Edition, one must stop the Automatic Updates service PRIOR
>>to running the above. This wasn't the case when doing so on XP Pro *
>>
>>The *last resort* is to delete DataStore.edb
>>
>>To mitigate log/database corruption, MS suggests this:
>>
>>Virus scanning recommendations for computers that are running Windows
>>Server 2003, Windows 2000, or Windows XP
>>http://support.microsoft.com/kb/822158
>>Last Review :October 30, 2006
>>
>> For computers that are running Windows Server 2003, Windows 2000, or
>>Windows XP
>>
>>Do not scan the following files and folders. These files are not at risk
>>of infection. If you scan these files, serious performance problems may
>>occur because of file locking.
>> Where a specific set of files is identified by name, exclude only
>>those files instead of the whole folder. Sometimes, the whole folder
>>must be excluded. Do not exclude any one of these based on the file name
>>extension. For example, do not exclude all files that have a .dit
>>extension. Microsoft has no control over other files that may use the
>>same extensions as the following files.
>>
>> • Microsoft Windows Update or Automatic Update related files
>> • The Windows Update or Automatic Update database file. This file
>>is located in the following folder:
>>%windir%\SoftwareDistribution\Datastore
>>
>> Exclude the Datastore.edb file.
>>
>> • The transaction log files. These files are located in the
>>following folder:
>> %windir%\SoftwareDistribution\Datastore\Logs
>> Exclude the following files:
>> • Edb*.log
>>
>>Note The wildcard character indicates that there may be several files.
>> • Res1.log
>> • Res2.log
>> • Edb.chk
>> • Tmp.edb
>>
>>MowGreen [MVP 2003-2007]
>>===============
>> *-343-* FDNY
>>Never Forgotten
>>===============
>>
>>
>>vpc5fan wrote:
>>
>>
>>>Your batch file will delete the update history for Microsoft Update. Is
>>>there a reason you feel that is needed?
>>>
>>>John
>>>
>>>
>>>"Bill Barrett - GatorPC" wrote:
>>>
>>>
>>>
>>>
>>>>Create a batch file:
>>>>---------------------------------------------------------------------------------------
>>>>@echo off
>>>>
>>>>net stop "Automatic Updates"
>>>>net stop "Background Intelligent Transfer Service"
>>>>
>>>>RD c:\windows\softwaredistribution /s /q
>>>>---------------------------------------------------------------------------------------
>>>
>>>

Thanks a lot for the information. I have XP Pro on 3 machines and XP Home on
one other. The XP pro machines all have Office 2003 but the XP Home machine
doesn't have Office. Not having any issues with the XP Home machine. I
will try the defrag first.

John

"MowGreen [MVP]" wrote:

> > * On XP Home Edition, one must stop the Automatic Updates service PRIOR
> > to running the above. This wasn't the case when doing so on XP Pro *
>
> The above was my finding on running esentutl. I ran the defrag command
> and it made a noticeable difference on a VPC install of XP HE.
> However, Office is not installed and the detection scan was done at
> Windows Update.
>
> The changes at WU/MS update include a new MSO.dll combined with the
> latest Windows Update Agent, and a newer version of msi.dll [KB927891].
>
> The changes *should* make a noticeable difference when scanning at MU,
> but if the database has already been damaged ... then it may not
> completely alleviate the issue.
> Give the defrag command a try and see if it helps any.
>
> MowGreen [MVP 2003-2007]
> ===============
> *-343-* FDNY
> Never Forgotten
> ===============
>
>
>
> vpc5fan wrote:
> > MowGreen,
> >
> > That looks like some good info. Do any services have to be stopped prior to
> > running the esentutl command with the switches you mentioned?
> >
> > Those commands you mentioned may be needed for the following:
> >
> > I have at least one machine that has had the latest KB927891 patch and
> > Windows Update Agent 3.0 installed and it no longer pegs my CPU however it
> > did still takes a longer than usual time "scanning" on Microsoft Update. It
> > may have been because I had reverted back to using Windows Update and Office
> > Update (have Office 2003) months ago until the working solution for this
> > issue came out. It did however find this months Windows and Office updates
> > and installed them just fine. I haven't decided whether to manually update
> > via Microsoft Update for a month or two just to make sure the svchost.exe
> > issue is fully resolved or just let AU press on and see what happens. I
> > figure I will have to manually update in order to see if I can fix the "long
> > scan time" issue.
> >
> >
> > John
> >
> > "MowGreen [MVP]" wrote:
> >
> >
> >>The update history viewable on MU/WU is stored in DataStore.edb which
> >>can become corrupted/fragmented due to scanning by antivirus software.
> >>There is another update history stored in ReportingEvents.log located in
> >>%windir%\SoftwareDistribution.
> >>
> >>The detection scan hits DataStore.edb causing a buffer overflow.
> >>One can run esentutl from a Command Prompt to defragment DataStore.edb
> >>instead of deleting it in hopes that will resolve the issue -
> >>
> >>esentutl /d %windir%\SoftwareDistribution\Datastore\datastore. edb
> >>
> >>If that doesn't resolve the issue, attempt to Recover the file -
> >>
> >>esentutl /r %windir%\SoftwareDistribution\Datastore\datastore. edb
> >>
> >>[This command performs recovery, bringing all databases to a
> >>consistent state]
> >>
> >>The next to last resort is to attempt to Repair it -
> >>
> >>esentutl /p %windir%\SoftwareDistribution\Datastore\datastore. edb
> >>
> >>NOTE: MS recommends that if the system is imaged regularly that a new
> >>system image be done after running ANY of the above operations
> >>
> >>* On XP Home Edition, one must stop the Automatic Updates service PRIOR
> >>to running the above. This wasn't the case when doing so on XP Pro *
> >>
> >>The *last resort* is to delete DataStore.edb
> >>
> >>To mitigate log/database corruption, MS suggests this:
> >>
> >>Virus scanning recommendations for computers that are running Windows
> >>Server 2003, Windows 2000, or Windows XP
> >>http://support.microsoft.com/kb/822158
> >>Last Review :October 30, 2006
> >>
> >> For computers that are running Windows Server 2003, Windows 2000, or
> >>Windows XP
> >>
> >>Do not scan the following files and folders. These files are not at risk
> >>of infection. If you scan these files, serious performance problems may
> >>occur because of file locking.
> >> Where a specific set of files is identified by name, exclude only
> >>those files instead of the whole folder. Sometimes, the whole folder
> >>must be excluded. Do not exclude any one of these based on the file name
> >>extension. For example, do not exclude all files that have a .dit
> >>extension. Microsoft has no control over other files that may use the
> >>same extensions as the following files.
> >>
> >> • Microsoft Windows Update or Automatic Update related files
> >> • The Windows Update or Automatic Update database file. This file
> >>is located in the following folder:
> >>%windir%\SoftwareDistribution\Datastore
> >>
> >> Exclude the Datastore.edb file.
> >>
> >> • The transaction log files. These files are located in the
> >>following folder:
> >> %windir%\SoftwareDistribution\Datastore\Logs
> >> Exclude the following files:
> >> • Edb*.log
> >>
> >>Note The wildcard character indicates that there may be several files.
> >> • Res1.log
> >> • Res2.log
> >> • Edb.chk
> >> • Tmp.edb
> >>
> >>MowGreen [MVP 2003-2007]
> >>===============
> >> *-343-* FDNY
> >>Never Forgotten
> >>===============
> >>
> >>
> >>vpc5fan wrote:
> >>
> >>
> >>>Your batch file will delete the update history for Microsoft Update. Is
> >>>there a reason you feel that is needed?
> >>>
> >>>John
> >>>
> >>>
> >>>"Bill Barrett - GatorPC" wrote:
> >>>
> >>>
> >>>
> >>>
> >>>>Create a batch file:
> >>>>---------------------------------------------------------------------------------------
> >>>>@echo off
> >>>>
> >>>>net stop "Automatic Updates"
> >>>>net stop "Background Intelligent Transfer Service"
> >>>>
> >>>>RD c:\windows\softwaredistribution /s /q
> >>>>---------------------------------------------------------------------------------------
> >>>
> >>>
>

You're mowst welcome. The latest Version of the Windows Update Agent is
being pushed out gradually. However, suggest you install it on the XP
Pro systems that have Office 2003 installed.
From the WSUS Blog -
http://blogs.technet.com/wsus/archiv...follow-up.aspx

> While we are engaged in a world-wide deployment of the new AU client (build .0374), this
> staged deployment is occurring in a wave which we expect to complete by early June. This
> means that for AU users, the new client bits will just automatically self update when
> visiting the site before mid –June, and for WSUS users, you will be able to download the
> bits after 5/22/2007 (or upgrade to WSUS 3.0 now).
>
> To make the client available earlier vs. waiting for the duration of the world-wide
> roll-out, we released the client in a ‘stand-alone’ form which you can download from the
> Download Center now. The version of the client is 0374 – and can be installed directly
> from:

http://download.windowsupdate.com/v7...gent30-x86.exe

Then install KB927891 as it updates the msi.dll :
http://www.microsoft.com/downloads/d...9-404327772E5A
Restart the systems

How are the systems faring now ?

MowGreen [MVP 2003-2007]
===============
*-343-* FDNY
Never Forgotten
===============


vpc5fan wrote:

> Thanks a lot for the information. I have XP Pro on 3 machines and XP Home on
> one other. The XP pro machines all have Office 2003 but the XP Home machine
> doesn't have Office. Not having any issues with the XP Home machine. I
> will try the defrag first.
>
> John
>
> "MowGreen [MVP]" wrote:
>
>
>>>* On XP Home Edition, one must stop the Automatic Updates service PRIOR
>>>to running the above. This wasn't the case when doing so on XP Pro *
>>
>>The above was my finding on running esentutl. I ran the defrag command
>>and it made a noticeable difference on a VPC install of XP HE.
>>However, Office is not installed and the detection scan was done at
>>Windows Update.
>>
>>The changes at WU/MS update include a new MSO.dll combined with the
>>latest Windows Update Agent, and a newer version of msi.dll [KB927891].
>>
>>The changes *should* make a noticeable difference when scanning at MU,
>>but if the database has already been damaged ... then it may not
>>completely alleviate the issue.
>>Give the defrag command a try and see if it helps any.
>>
>>MowGreen [MVP 2003-2007]
>>===============
>> *-343-* FDNY
>>Never Forgotten
>>===============
>>
>>
>>
>>vpc5fan wrote:
>>
>>>MowGreen,
>>>
>>>That looks like some good info. Do any services have to be stopped prior to
>>>running the esentutl command with the switches you mentioned?
>>>
>>>Those commands you mentioned may be needed for the following:
>>>
>>>I have at least one machine that has had the latest KB927891 patch and
>>>Windows Update Agent 3.0 installed and it no longer pegs my CPU however it
>>>did still takes a longer than usual time "scanning" on Microsoft Update. It
>>>may have been because I had reverted back to using Windows Update and Office
>>>Update (have Office 2003) months ago until the working solution for this
>>>issue came out. It did however find this months Windows and Office updates
>>>and installed them just fine. I haven't decided whether to manually update
>>>via Microsoft Update for a month or two just to make sure the svchost.exe
>>>issue is fully resolved or just let AU press on and see what happens. I
>>>figure I will have to manually update in order to see if I can fix the "long
>>>scan time" issue.
>>>
>>>
>>>John
>>>
>>>"MowGreen [MVP]" wrote:
>>>
>>>
>>>
>>>>The update history viewable on MU/WU is stored in DataStore.edb which
>>>>can become corrupted/fragmented due to scanning by antivirus software.
>>>>There is another update history stored in ReportingEvents.log located in
>>>>%windir%\SoftwareDistribution.
>>>>
>>>>The detection scan hits DataStore.edb causing a buffer overflow.
>>>>One can run esentutl from a Command Prompt to defragment DataStore.edb
>>>>instead of deleting it in hopes that will resolve the issue -
>>>>
>>>>esentutl /d %windir%\SoftwareDistribution\Datastore\datastore. edb
>>>>
>>>>If that doesn't resolve the issue, attempt to Recover the file -
>>>>
>>>>esentutl /r %windir%\SoftwareDistribution\Datastore\datastore. edb
>>>>
>>>>[This command performs recovery, bringing all databases to a
>>>>consistent state]
>>>>
>>>>The next to last resort is to attempt to Repair it -
>>>>
>>>>esentutl /p %windir%\SoftwareDistribution\Datastore\datastore. edb
>>>>
>>>>NOTE: MS recommends that if the system is imaged regularly that a new
>>>>system image be done after running ANY of the above operations
>>>>
>>>>* On XP Home Edition, one must stop the Automatic Updates service PRIOR
>>>>to running the above. This wasn't the case when doing so on XP Pro *
>>>>
>>>>The *last resort* is to delete DataStore.edb
>>>>
>>>>To mitigate log/database corruption, MS suggests this:
>>>>
>>>>Virus scanning recommendations for computers that are running Windows
>>>>Server 2003, Windows 2000, or Windows XP
>>>>http://support.microsoft.com/kb/822158
>>>>Last Review :October 30, 2006
>>>>
>>>> For computers that are running Windows Server 2003, Windows 2000, or
>>>>Windows XP
>>>>
>>>>Do not scan the following files and folders. These files are not at risk
>>>>of infection. If you scan these files, serious performance problems may
>>>>occur because of file locking.
>>>> Where a specific set of files is identified by name, exclude only
>>>>those files instead of the whole folder. Sometimes, the whole folder
>>>>must be excluded. Do not exclude any one of these based on the file name
>>>>extension. For example, do not exclude all files that have a .dit
>>>>extension. Microsoft has no control over other files that may use the
>>>>same extensions as the following files.
>>>>
>>>> • Microsoft Windows Update or Automatic Update related files
>>>> • The Windows Update or Automatic Update database file. This file
>>>>is located in the following folder:
>>>>%windir%\SoftwareDistribution\Datastore
>>>>
>>>> Exclude the Datastore.edb file.
>>>>
>>>> • The transaction log files. These files are located in the
>>>>following folder:
>>>> %windir%\SoftwareDistribution\Datastore\Logs
>>>> Exclude the following files:
>>>> • Edb*.log
>>>>
>>>>Note The wildcard character indicates that there may be several files.
>>>> • Res1.log
>>>> • Res2.log
>>>> • Edb.chk
>>>> • Tmp.edb
>>>>
>>>>MowGreen [MVP 2003-2007]
>>>>===============
>>>> *-343-* FDNY
>>>>Never Forgotten
>>>>===============
>>>>
>>>>
>>>>vpc5fan wrote:
>>>>
>>>>
>>>>
>>>>>Your batch file will delete the update history for Microsoft Update. Is
>>>>>there a reason you feel that is needed?
>>>>>
>>>>>John
>>>>>
>>>>>
>>>>>"Bill Barrett - GatorPC" wrote:
>>>>>
>>>>>
>>>>>
>>>>>
>>>>>
>>>>>>Create a batch file:
>>>>>>---------------------------------------------------------------------------------------
>>>>>>@echo off
>>>>>>
>>>>>>net stop "Automatic Updates"
>>>>>>net stop "Background Intelligent Transfer Service"
>>>>>>
>>>>>>RD c:\windows\softwaredistribution /s /q
>>>>>>---------------------------------------------------------------------------------------
>>>>>
>>>>>