Windows directory: $hf_mig$

Posted: 07-10-2007, 01:12 PM
I'm running windows xp sp2 an looking in the c:\windows directory, the first
sub directory is the on above $hf_mig$.

In looking at the contents of this directory I see all the windows updates
in sub-directories.

Do I need to keep these files? Or can I delete them without causing problems
in running windows?

Any help appreciated

Regards,


Reply With Quote

Responses to "Windows directory: $hf_mig$"

Patti MacLeod
Guest
Posts: n/a
 
RE: Windows directory: $hf_mig$
Posted: 07-10-2007, 03:22 PM
Hi Bullwinkle,

You should keep those files. Have a look here for a description of the
function of that folder:

Description of the contents of Windows XP Service Pack 2 and Windows Server
2003 software update packages
http://support.microsoft.com/default.aspx?scid=824994
Scroll down to the "Notes" section



Regards,

--
Patti MacLeod
Microsoft MVP - Windows Shell/User


"Bullwinkle" wrote:
> I'm running windows xp sp2 an looking in the c:\windows directory, the first
> sub directory is the on above $hf_mig$.
>
> In looking at the contents of this directory I see all the windows updates
> in sub-directories.
>
> Do I need to keep these files? Or can I delete them without causing problems
> in running windows?
>
> Any help appreciated
>
> Regards,
>
>
>
Reply With Quote
cquirke (MVP Windows shell/user)
Guest
Posts: n/a
 
Re: Windows directory: $hf_mig$
Posted: 07-11-2007, 11:01 AM
On Tue, 10 Jul 2007 07:22:01 -0700, Patti MacLeod
>You should keep those files. Have a look here for a description of the
>function of that folder:
>
>Description of the contents of Windows XP Service Pack 2 and Windows Server
>2003 software update packages
>http://support.microsoft.com/default.aspx?scid=824994
>Scroll down to the "Notes" section
You can keep them, but not have them clogging up C:, if you have a
small C: volume that is intended to operate as a lean, fast "engine
room". As it is, for every 1 active code file, you can end up with 3
inactive forms of the same file (DLL cache, patch backup version,
patch new vserion). I can't see a 75% dead-weight overhead tolerated
anywhere else (75% RAM unused, 75% CPU cycles unused), can you?

That way, if you need to "undo" a patch, you can copy the material
back to C: before doing so.

If you follow this approach, you can free about 600M to over 1G on C:,
just by moving off the main $hf_mig$ subtree and the other $..$
subtrees that follow it.

That's before you look at "harder" bloat targets, like Installer,
ServicePackFiles, Downloaded Installations and SoftwareDistribution.
Of those, I generally only relocate ServicePackFiles.

However, if you do relocate these, it's important to keep layering the
relocated set with new stuff as it is spawned by updates etc. else the
subtree will no longer be complete and accurate.


>------------------------- ---- --- -- - - - -
I'm on a ten-year lunch break
>------------------------- ---- --- -- - - - -
Reply With Quote
Bullwinkle
Guest
Posts: n/a
 
Re: Windows directory: $hf_mig$
Posted: 07-12-2007, 12:23 AM
Thank you Patti. I basically just want to know if this is wasted space. I
have plenty of room to keep them there.

Regards,

"Patti MacLeod" <pam120@nospamshaw.ca> wrote in message
news:6B0E9C26-0C47-4FBF-B40B-F77F90133994@microsoft.com...
> Hi Bullwinkle,
>
> You should keep those files. Have a look here for a description of the
> function of that folder:
>
> Description of the contents of Windows XP Service Pack 2 and Windows
> Server
> 2003 software update packages
> http://support.microsoft.com/default.aspx?scid=824994
> Scroll down to the "Notes" section
>
>
>
> Regards,
>
> --
> Patti MacLeod
> Microsoft MVP - Windows Shell/User
>
>
> "Bullwinkle" wrote:
>
>> I'm running windows xp sp2 an looking in the c:\windows directory, the
>> first
>> sub directory is the on above $hf_mig$.
>>
>> In looking at the contents of this directory I see all the windows
>> updates
>> in sub-directories.
>>
>> Do I need to keep these files? Or can I delete them without causing
>> problems
>> in running windows?
>>
>> Any help appreciated
>>
>> Regards,
>>
>>
>>

Reply With Quote
Bullwinkle
Guest
Posts: n/a
 
Re: Windows directory: $hf_mig$
Posted: 07-12-2007, 12:24 AM
Thank you for the info.

Regards,

"cquirke (MVP Windows shell/user)" <cquirkenews@nospam.mvps.org> wrote in
message news:v1a993teblgl0e94stekgoe8i1lncpiura@4ax.com...
> On Tue, 10 Jul 2007 07:22:01 -0700, Patti MacLeod
>
>>You should keep those files. Have a look here for a description of the
>>function of that folder:
>>
>>Description of the contents of Windows XP Service Pack 2 and Windows
>>Server
>>2003 software update packages
>>http://support.microsoft.com/default.aspx?scid=824994
>>Scroll down to the "Notes" section
>
> You can keep them, but not have them clogging up C:, if you have a
> small C: volume that is intended to operate as a lean, fast "engine
> room". As it is, for every 1 active code file, you can end up with 3
> inactive forms of the same file (DLL cache, patch backup version,
> patch new vserion). I can't see a 75% dead-weight overhead tolerated
> anywhere else (75% RAM unused, 75% CPU cycles unused), can you?
>
> That way, if you need to "undo" a patch, you can copy the material
> back to C: before doing so.
>
> If you follow this approach, you can free about 600M to over 1G on C:,
> just by moving off the main $hf_mig$ subtree and the other $..$
> subtrees that follow it.
>
> That's before you look at "harder" bloat targets, like Installer,
> ServicePackFiles, Downloaded Installations and SoftwareDistribution.
> Of those, I generally only relocate ServicePackFiles.
>
> However, if you do relocate these, it's important to keep layering the
> relocated set with new stuff as it is spawned by updates etc. else the
> subtree will no longer be complete and accurate.
>
>
>
>>------------------------- ---- --- -- - - - -
> I'm on a ten-year lunch break
>>------------------------- ---- --- -- - - - -

Reply With Quote
Patti MacLeod
Guest
Posts: n/a
 
Re: Windows directory: $hf_mig$
Posted: 07-12-2007, 12:34 AM
You're welcome :-)



Regards,

--
Patti MacLeod
Microsoft MVP - Windows Shell/User


"Bullwinkle" wrote:
> Thank you Patti. I basically just want to know if this is wasted space. I
> have plenty of room to keep them there.
>
Reply With Quote
LadyDungeness@Fish.Net
Guest
Posts: n/a
 
Re: Windows directory: $hf_mig$
Posted: 07-13-2007, 10:56 AM
So, If I move the $hf_mig$ subtree & folders to my G drive, will
future updates know to add their folders there? Should I make a
redirect command or regkey someplace? Should I just add new $hf_mig$
subfolders as they accumulate?

Thanks.

`
Lady Dungeness
Crabby, but Delicious!
~~~~~~~~~~~~~~~~~~~~~~


On Wed, 11 Jul 2007 12:01:10 +0200, "cquirke (MVP Windows shell/user)"
<cquirkenews@nospam.mvps.org> wrote:

|On Tue, 10 Jul 2007 07:22:01 -0700, Patti MacLeod
|
|>You should keep those files. Have a look here for a description of the
|>function of that folder:
|>
|>Description of the contents of Windows XP Service Pack 2 and Windows Server
|>2003 software update packages
|>http://support.microsoft.com/default.aspx?scid=824994
|>Scroll down to the "Notes" section
|
|You can keep them, but not have them clogging up C:, if you have a
|small C: volume that is intended to operate as a lean, fast "engine
|room". As it is, for every 1 active code file, you can end up with 3
|inactive forms of the same file (DLL cache, patch backup version,
|patch new vserion). I can't see a 75% dead-weight overhead tolerated
|anywhere else (75% RAM unused, 75% CPU cycles unused), can you?
|
|That way, if you need to "undo" a patch, you can copy the material
|back to C: before doing so.
|
|If you follow this approach, you can free about 600M to over 1G on C:,
|just by moving off the main $hf_mig$ subtree and the other $..$
|subtrees that follow it.
|
|That's before you look at "harder" bloat targets, like Installer,
|ServicePackFiles, Downloaded Installations and SoftwareDistribution.
|Of those, I generally only relocate ServicePackFiles.
|
|However, if you do relocate these, it's important to keep layering the
|relocated set with new stuff as it is spawned by updates etc. else the
|subtree will no longer be complete and accurate.
|
|
|
|>------------------------- ---- --- -- - - - -
| I'm on a ten-year lunch break
|>------------------------- ---- --- -- - - - -
Reply With Quote
cquirke (MVP Windows shell/user)
Guest
Posts: n/a
 
Re: Windows directory: $hf_mig$
Posted: 07-16-2007, 03:54 AM
On Fri, 13 Jul 2007 02:56:56 -0700, LadyDungeness@Fish.Net wrote:
>So, If I move the $hf_mig$ subtree & folders to my G drive, will
>future updates know to add their folders there?
No. A new $hf_mig$ will be spawned in %WinDir% again.
>Should I make a redirect command or regkey someplace?
AFAIK it's hard-coded, hence...

http://cquirke.spaces.live.com/blog/...8C23!302.entry
>Should I just add new $hf_mig$
>subfolders as they accumulate?
That's what I've been doing :-)


>--------------- ---- --- -- - - - -
Saws are too hard to use.
Be easier to use!
>--------------- ---- --- -- - - - -
Reply With Quote
 
LinkBack Thread Tools Display Modes
Reply


Thread Tools
Display Modes

Posting Rules
You may not post new threads
You may post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is On
HTML code is Off
Trackbacks are On
Pingbacks are On
Refbacks are On


Similar Threads
Thread Thread Starter Forum Replies Last Post
Max Number of Photos in Directory / Max Directory Size Charax Windows XP Photos 0 11-18-2005 02:15 PM
C drive bloat: $hf_mig$ folder?? John Vinson Windows XP Configuration & Management 4 05-18-2005 12:59 PM
Active Directory directory services administrative tools Daane Clifford Windows XP Security & Administration 0 08-20-2003 11:33 PM
Can Windows XP Home edition join Windows 2000 active directory ?? Altezza 5.0 Windows XP Network & Web 1 07-24-2003 02:17 PM
Can Windows XP Home edition join Windows 2000 active directory ?? Altezza 5.0 Windows XP Basics 3 07-24-2003 05:11 AM


1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 61 62 63 64 65 66 67 68 69 70 71 72 73 74 75 76 77 78 79 80 81 82 83 84 85 86 87 88 89 90