RE: Windows Update not cleaning up after itself on D: drive

  • Thread starter Thread starter Frank H
  • Start date Start date
F

Frank H

Guest
RE: Windows Update not cleaning up after itself on D: drive

This is a change to the Kaseya program where the folder name scheme has been
changed from the machine name to a universal GUID. If you delete this
folders, then Kaseya will re-download all of the updates to be installed
locally.

Similar questions can be answered at this website:
http://www.securemycompany.com/kaseya

Frank
Hosted Kaseya Managed Services Software

"TaurArian" wrote:

> Might relate to these two updates: KB927978 and KB925672
>
> Mow's blog
> http://mowgreen.castlecops.com/archives/2007/01/fix_kb927978_and_kb925672_repe.html
>
> <snip>
> In addition, KB927978 generates randomly named folders on either the root
> drive, usually C:\ , or on the drive with the most free space, for each
> attempt at installing it. The folders contain the installation log file.
> These folders can be safely deleted. <snip>
>
>
> "Joe Grover" wrote:
>
> > Over the last couple of weeks I am finding random machines that have a D:
> > drive not having Windows Update folders removed after updates have been
> > applied and the system is rebooted.
> >
> > In my NOC I have several 2000 and 2003 servers that receive their updates
> > via a product
> > called Kaseya, and I was thinking it had something to do with that as it
> > began shortly after we applied some updates to Kaseya and modified our patch
> > management process.
> >
> > However I just noticed that my home PC (Windows XP Professional that is not
> > managed by anything in our office, heh) also has these folders.
> >
> > The folders are strings of alphanumeric characters (like
> > 3bc8f5b8d03c903ca7d63db2 and 7f7b9ea31a8cf5cf1447fcac817788a5) and each of
> > them contains a folder called "update". The contents of this folder varies
> > depending on what the specific patch is for. Many of the folders on my
> > Windows 2000 servers contain only a 43KB file called "iecustom.dll". My
> > home PC has folders like:
> >
> > D:\0c4842dab66d248996f219c973\update\update.exe and updspapi.dll
> > D:\bd0ba71534a1b8b54eb3ee176b69\update\updspapi.dll
> > D:\fb2af0e560a2d943c6103526\update\update.exe and wgawizard.dll
> >
> > I don't see these folders on the C: drives of any of the machines I've
> > looked
> > at, and it doesn't affect all machines with a D: drive (such as our Windows
> > 2003/Exchange 2003 server).
> >
> > What could be causing this? I'm sure I can probably remove the folders, but
> > I'm wondering if this is just something buggy with a recent update that's
> > caused this? The XP machine I have at home was just reloaded and these
> > folders showed up upon running the initial batch of critical updates using
> > Windows Update.
> >
> >
> > Joe
> >
> >
> >
> >
 
RE: Windows Update not cleaning up after itself on D: drive

RE: Windows Update not cleaning up after itself on D: drive

Sorry ...wrong URL.

http://www.securemycompany.com/Services/Kaseya

Frank

"Frank H" wrote:

>
> This is a change to the Kaseya program where the folder name scheme has been
> changed from the machine name to a universal GUID. If you delete this
> folders, then Kaseya will re-download all of the updates to be installed
> locally.
>
> Similar questions can be answered at this website:
> http://www.securemycompany.com/kaseya
>
> Frank
> Hosted Kaseya Managed Services Software
>
> "TaurArian" wrote:
>
> > Might relate to these two updates: KB927978 and KB925672
> >
> > Mow's blog
> > http://mowgreen.castlecops.com/archives/2007/01/fix_kb927978_and_kb925672_repe.html
> >
> > <snip>
> > In addition, KB927978 generates randomly named folders on either the root
> > drive, usually C:\ , or on the drive with the most free space, for each
> > attempt at installing it. The folders contain the installation log file.
> > These folders can be safely deleted. <snip>
> >
> >
> > "Joe Grover" wrote:
> >
> > > Over the last couple of weeks I am finding random machines that have a D:
> > > drive not having Windows Update folders removed after updates have been
> > > applied and the system is rebooted.
> > >
> > > In my NOC I have several 2000 and 2003 servers that receive their updates
> > > via a product
> > > called Kaseya, and I was thinking it had something to do with that as it
> > > began shortly after we applied some updates to Kaseya and modified our patch
> > > management process.
> > >
> > > However I just noticed that my home PC (Windows XP Professional that is not
> > > managed by anything in our office, heh) also has these folders.
> > >
> > > The folders are strings of alphanumeric characters (like
> > > 3bc8f5b8d03c903ca7d63db2 and 7f7b9ea31a8cf5cf1447fcac817788a5) and each of
> > > them contains a folder called "update". The contents of this folder varies
> > > depending on what the specific patch is for. Many of the folders on my
> > > Windows 2000 servers contain only a 43KB file called "iecustom.dll". My
> > > home PC has folders like:
> > >
> > > D:\0c4842dab66d248996f219c973\update\update.exe and updspapi.dll
> > > D:\bd0ba71534a1b8b54eb3ee176b69\update\updspapi.dll
> > > D:\fb2af0e560a2d943c6103526\update\update.exe and wgawizard.dll
> > >
> > > I don't see these folders on the C: drives of any of the machines I've
> > > looked
> > > at, and it doesn't affect all machines with a D: drive (such as our Windows
> > > 2003/Exchange 2003 server).
> > >
> > > What could be causing this? I'm sure I can probably remove the folders, but
> > > I'm wondering if this is just something buggy with a recent update that's
> > > caused this? The XP machine I have at home was just reloaded and these
> > > folders showed up upon running the initial batch of critical updates using
> > > Windows Update.
> > >
> > >
> > > Joe
> > >
> > >
> > >
> > >
 
Back
Top