Re: C:\WINDOWS\$hf_mig$ = Correctives?

Tech Tip: Click here to run a free scan for Windows Errors and optimize PC performance



In news:ewQj%23nn7FHA.2040@xxxxxxxxxxxxxxxxxxxx,
TaurArian [MVP] <taurarianREMOVECAPS@xxxxxxxxxxx> typed:
> No.
>
> Description of the contents of Windows XP Service Pack 2 and Windows
> Server 2003 software update packages
> http://support.microsoft.com/default.aspx?scid=kb;en-us;824994
>
>
> From the above article:-
>
> When a security update, critical update, update, update rollup,
> driver, or feature pack installs GDR version files, the hotfix files
> are also copied to the %windir%\$hf_mig$ folder. This supports
> migration to the appropriate files if you later install a hotfix or
> service pack that includes earlier versions of these files. For
> example, consider the following scenario:
> 1. You apply a security update that installs a GDR version of
> File.dll with a version number of 5.2.3790.1000 and copies a hotfix
> version of File.dll with a version number of 5.2.3790.1000 to the
> %windir%\$hf_mig$ folder.
> 2. You apply a hotfix that includes a hotfix version of File.dll
> with a version number of 5.2.3790.0000.
>
> In this scenario the hotfix installation in step 2 installs the
> hotfix version of File.dll (version number 5.2.3790.1000) from the
> %windir%\$hf_mig$ folder instead of the hotfix version of File.dll
> (version number 5.2.3790.0000) from the hotfix package.

My question is, why in the world would Microsoft be issuing a hotfix with
and older version of a file in the first place, if in the past updates a
newer version has already been used? Doesn't Microsoft have records of it's
files and their numbers? Or is it just, "Oh well, don't have time to look
for a later version of this file...just put this version in the 'fix'."
Maybe, just maybe, that's what there are patches to repair patches with
Microsoft products?

....Allen

>
>
>
>
> "Dave Neve" <NoAddressForSpammers@xxxxxxx> wrote in message
> news:eXkHWol7FHA.3880@xxxxxxxxxxxxxxxxxxxxxxx
>> Hello
>>
>> I am going to reinstall Windows soon and I am wondering if I can
>> 'keep' my updates, esp as I may not have a Broadband connection
>> immediately. I have found the folder C:\WINDOWS\$hf_mig$ which seems to
>> have the
>> correctives. I've noticed an 'update.exe with each corrective and I am
>> wondering
>> if this can be clicked on.
>>
>> Finally, I assume that the correctives are still valid whatever the
>> changes made to the computer (new motherboard and processor in this
>> case). Can sm please confirm or put me straight?
>>
>> Thanks
>>
>> Dave Neve



.



Relevant Pages

  • RE: Windows shutting down..window freezes
    ... When you try to shut down your computer that is running Microsoft Windows ... 2000 Service Pack 3, ... A supported hotfix is now available from Microsoft, ...
    (microsoft.public.win2000.file_system)
  • Re: download folder
    ... Description of the contents of Windows XP Service Pack 2 and Windows Server 2003 software ... %windir%\$hf_mig$ folder ... the hotfix files are also copied to the %windir%\$hf_mig$ ... You apply a security update that installs a GDR version of File.dll with a version ...
    (microsoft.public.windowsupdate)
  • Re: download folder
    ... Description of the contents of Windows XP Service Pack 2 and Windows Server 2003 software ... %windir%\$hf_mig$ folder ... the hotfix files are also copied to the %windir%\$hf_mig$ ... You apply a security update that installs a GDR version of File.dll with a version ...
    (microsoft.public.windowsupdate)
  • Re: SP4 reverts MS03-026 - Not!
    ... Windows 2000 does implement by default Windows File ... This may be what is actually returning the hotfix file ... version after the service pack overwrites it (latest file version should ... Summer's Hottest Certification Just Got HOTTER! ...
    (NT-Bugtraq)
  • RE: Important information about XP SP2 .ADM Files
    ... Though when I go to the link it says I must call to get the hotfix is ... > Windows XP Service Pack 2. ... > associated with this service pack, ... > your attention to an important issue related to Group Policy. ...
    (microsoft.public.win2000.group_policy)