FAQ / Common Problems & Solutions


Recommended Posts

GREAT!!!!

NOW you tell me! J/K, LOL

Seriously, why is that folder even there and consuming 135MB of my hard drive space and also containing uninstall information.

I think my questions are being answered which is that if I want to streamline my install without having all of these packages there then I need to use Nlite but if I don't mind wasting my HD space then I can use autopatcher.

You'd think that if I deleted the $ntuninstall folders that I'd get rid of the updates but nope, they're still there under $hf_mig.

Anyhow, thanks for your help guys - I've learned something from the exchange.

^ you really want to know what it is, read this

in a nutshell (or as simple as i can make it):

in microsofts development enviroment they have two copies of windows on which they create and test updates, one with just general publicly available updates, and one with hotfixes (quick updates that havent been put through full testing like other updates). when updates are put together, they will include two copies (if there is a hotfix'd one, else just one). when the update is installed it will check to see if any of the files being updated are hotfix versions, and if so install the hotfix copies. if not then the hotfix copies are stored in the $hf_mig$ folder (hotfix migration) incase they are needed in future.

it might seem complicated and confusing keeping two copies of the files like this, but there is an example given on the page i linked to which explains exactly why the hotfix copies are needed to be kept. and the reason for existance of hotfix copies in the first place is because they are used to provide quick fix solutions to problems in corporate systems.

so, you can remove the uninstall folders (i do) and use ccleaner to cleanup the add/remove and other registry entries. you could also uncheck the autopatcher 'keep backups' option on the selection page when installing updates which should prevent them being created in the first place.

however, even with nlite you must always keep the $hf_mig$ folder else in the future your system could become unstable, or produce errors due to file incompatabilities because the backed up hotfix copy of a file wasnt present.

Edited by theblazingangel

Hy !

My company is using a proxy server to acces the internet and because of that server I can't update my WIN2KSP4. Recently I have problems with my OS and I have decided to reinstall it, after that I use Autopacher 2000 April Full release. After running Autopatcher I can't acces the internet because the browser (IE and Mozilla) don't recognize the proxy even though the settings (proxy IP adress and port) are correct.

Can some one help me to solve this problem ?

^ right, well thats because your trying to use an update release on its own. you need a 'full' or 'lite' release as a base to install update releases onto.

e.g.

to have the latest stuff you could do this:

april06 full/lite + may06 update + june06 update ....

or this:

dec05 full/lite + jan06 update + feb06 update + mar06 update + apr06 update + may06 update ....

update releases are used to update autopatcher with the latest copy of files. they save you from downloading new large full or lite release every month. they should not be used on there own.

@silversf, sorry but i really dont know the answer to your problem, and by the lack of replies no-one else seems to, if you cant find the answer through google i suggest you re-install windows again and do some experimenting to find out what in autopatcher caused the problem, once you know that then you can narrow down the search for an answer.

  theblazingangel said:

^ right, well thats because your trying to use an update release on its own. you need a 'full' or 'lite' release as a base to install update releases onto.

e.g.

to have the latest stuff you could do this:

april06 full/lite + may06 update + june06 update ....

or this:

dec05 full/lite + jan06 update + feb06 update + mar06 update + apr06 update + may06 update ....

update releases are used to update autopatcher with the latest copy of files. they save you from downloading new large full or lite release every month. they should not be used on there own.

@silversf, sorry but i really dont know the answer to your problem, and by the lack of replies no-one else seems to, if you cant find the answer through google i suggest you re-install windows again and do some experimenting to find out what in autopatcher caused the problem, once you know that then you can narrow down the search for an answer.

Thanx for your reply_response_guidance...Really appreciate it_very much...

6) When i double click the AutoPatcher shortcut nothing happens

Go to: C:\Program Files\AutoPatcher\tools, run 'AutoPatcher Module Editor.exe' and close it - next run autopatcher.

If that doesn't help, copy comdlg32.ocx from the AutoPatcher \bin folder to c:\windows\system32 (overwrite existing file if there is one).

I have this problem as mentioned-above. So I tried both the recommendations but it didn't work.

Actually it all started like this: I have April Full 2006 installed and it was working well. Then I downloaded and installed the May 2006 update (installation was successful). I double-clicked on the Auto Patcher shortcut but nothing happened. So I tried the above recommendations. But it didn't resolve the problem. This time I uninstalled and re-installed the April Full 2006 and May Update 2006. And again tried the above methods and still now facing the same problem. I am using Windows XP SP2 32-bit. Please help!!

ok this is a A1 idea and thank you very much its free dont get much these days for free lol.

ok i read most posts and i still dont under stand why i cannot update my may update any help would be cool.

what i have done so for is

only installed April full version and full update pack but when i install may i get a message saying an existing autopatcher installation was not detected in the install directory, if you continue you may experience problems

have 2 autopatch folders in my c drive one called *AutoPatcher 2K* and the other is *AutoPatcher*

i have tried deleting folders and contents of folders in modules and then tried to reinstall may update

i have reinstall the full version of April autopatcher with no luck but it did say if you uninstall this programme you will not be able to install next months update so ill a bit lost be great to use it every month

hope this make sense as im not good with words :>

^ youve mixed up windows 2000 and windows xp releases, thats why youve got the two different folders ('autopatcher' and 'autopatcher 2k'). the error occurs because the update release is trying to install to one folder while the full release is installed in another.

  theblazingangel said:

^ youve mixed up windows 2000 and windows xp releases, thats why youve got the two different folders ('autopatcher' and 'autopatcher 2k'). the error occurs because the update release is trying to install to one folder while the full release is installed in another.

^yep you were right 2k was 2000 not xp well done ..

im all working and up to date thank you so much for your time :>

and i will pop in and read the forums :cool:

great stuff

When i double click the AutoPatcher shortcut nothing happens-

Go to: C:\Program Files\AutoPatcher\tools, run 'AutoPatcher Module Editor.exe' and close it - next run autopatcher.

If that doesn't help, copy comdlg32.ocx from the AutoPatcher \bin folder to c:\windows\system32 (overwrite existing file if there is one).

I looked at the folder and all that's in there is 'modules' folder and the uninstall tool. I don't quite understand what or how to"copy comdlg32.ocx from the AutoPatcher \bin folder to c:\windows\system32 (overwrite existing file if there is one"

Can anyone dumb that down for me?

Thanks!

  vantuz said:

6) When i double click the AutoPatcher shortcut nothing happens

Go to: C:\Program Files\AutoPatcher\tools, run 'AutoPatcher Module Editor.exe' and close it - next run autopatcher.

If that doesn't help, copy comdlg32.ocx from the AutoPatcher \bin folder to c:\windows\system32 (overwrite existing file if there is one).

I have this problem as mentioned-above. So I tried both the recommendations but it didn't work.

Actually it all started like this: I have April Full 2006 installed and it was working well. Then I downloaded and installed the May 2006 update (installation was successful). I double-clicked on the Auto Patcher shortcut but nothing happened. So I tried the above recommendations. But it didn't resolve the problem. This time I uninstalled and re-installed the April Full 2006 and May Update 2006. And again tried the above methods and still now facing the same problem. I am using Windows XP SP2 32-bit. Please help!!

I had the same problem, I was doing a clean install of XP w/sp2 for my cousin, I installed April full 2006 and it didnt work, even after I tried the suggestions, I then uninstalled and reinstalled it and tried the suggestions again, I did it 3 times, so the 4th time I installed it I installed the May 2006 update as well same problem. After trying the same thing another 3 times I uninstalled again and I copied mfc42.dll to the system32 dir, and I installed the April 2006 full and it worked like a charm, after I'm done installing the updates I'm going to try it with the May update 2006 and I let you know if it works. Hope it works for you too.

problmem or not

i install the full version of april autopatcher.....all ok ...then i want to install the updates of may autopatcher ...i get the little verion ...so when i look in add/remov prog.. to see the updates ...nothing only 2-3 hotfix and something to wmp10 ...all the april update are gone...

what i'am doing rong ?....

what i need to do before installing some updates of autopatcher..?

  Agent9 said:

I had the same problem, I was doing a clean install of XP w/sp2 for my cousin, I installed April full 2006 and it didnt work, even after I tried the suggestions, I then uninstalled and reinstalled it and tried the suggestions again, I did it 3 times, so the 4th time I installed it I installed the May 2006 update as well same problem. After trying the same thing another 3 times I uninstalled again and I copied mfc42.dll to the system32 dir, and I installed the April 2006 full and it worked like a charm, after I'm done installing the updates I'm going to try it with the May update 2006 and I let you know if it works. Hope it works for you too.

tried it. still facing the same problem. i am giving up :no:

  MAdbUSU said:

problmem or not

i install the full version of april autopatcher.....all ok ...then i want to install the updates of may autopatcher ...i get the little verion ...so when i look in add/remov prog.. to see the updates ...nothing only 2-3 hotfix and something to wmp10 ...all the april update are gone...

what i'am doing rong ?....

what i need to do before installing some updates of autopatcher..?

have you actually run the autopatche program?

installing the releases simply extracts the program, you then need to run it to install the updates.

I have this problem:

6) When i double click the AutoPatcher shortcut nothing happens

Go to: C:\Program Files\AutoPatcher\tools, run 'AutoPatcher Module Editor.exe' and close it - next run autopatcher.

If that doesn't help, copy comdlg32.ocx from the AutoPatcher \bin folder to c:\windows\system32 (overwrite existing file if there is one).

But I have not resolved it...

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

    • No registered users viewing this page.
  • Posts

    • PC manufacturers used to trick BIOS copyright strings to get full editions of trial software by Usama Jawad You may have noticed that when you purchase a new PC, it comes with certain software pre-installed. Sometimes, when you open this software, it activates, and you receive the full version of it without paying any additional cost. This is because that PC's manufacturer is a licensee of that software and the fact that a customer gets the full version of a trial software for free serves as a perk for potential buyers. However, many PC manufacturers tried to trick this process in its infancy. During the days of Windows 95, when the Plug and Play specification was still in development, the OS' engineering team was trying to figure out ways through which it could identify PCs that existed prior to the inception of this specification. To that end, one of the methods they tried was searching for copyright strings and firmware dates in the BIOS. Through the course of this investigation, they discovered a rather oddly named copyright string "Not Copyright Fabrikam Computer" in a PC that was actually manufactured by Contoso. In this case, both Fabrikam and Contoso are fictional names that are used to describe this scenario without revealing the actual identity of the OEMs involved. Microsoft engineer Raymond Chen explains in a blog post that these odd copyright strings were actually appearing because Contoso PCs contained a trial version of a software and the company wanted the full version to be activated for customers even though it was not an official licensee. In order to bypass the costly licensing process, what the firm did was that it added the following text to its copyright string: "Copyright Contoso Not Copyright Fabrikam Computer". The trial version of said software would search for the string "Copyright Fabrikam Computer" and end up finding it within the substring of the convoluted copyright string mentioned above, accidentally activating the software's full version. While more robust ways were adopted later to avoid this problem, it's certainly interesting to see that OEMs would go to this length in order to distribute software that they are not officially allowed to. Well, as they say, the past stays in the past.
    • Uhm... a couple of issues with this. First, you're engaging in revisionist history. People weren't dragged from Win 7 to Win 10. You've kind of glossed over a whole cycle there: Win 8/8.1. People stayed on 7 because they hated 8/8.1 and held on until 10 showed up. THEN they actually started to switch voluntarily. Second, it's not about the OS, it's about the workflow. OS fans consistently miss this. People have work to do and they've invested a lot of time, effort and even money building their workflows. It's expensive to change so, that change has to offer real benefits that compensate for the cost of updating workflow and sorry, Win 11 just doesn't. That's the same reason they won't just jump to an entirely new OS - which has an even bigger workflow cost - until there's just no other option. Not only is there the core workflow cost, but the cost of finding new parallel software for the new OS, transferring and possible converting files and dealing with incompatibilities and then redeveloping workflows. It's just not as simple as "switch". And now there IS another option, stay on Win 10 for another year and pray for Win 12 (much as Win 7 users did with Win 8 - which happened when Win 10 came out).
  • Recent Achievements

    • Week One Done
      DrRonSr earned a badge
      Week One Done
    • Week One Done
      Sharon dixon earned a badge
      Week One Done
    • Dedicated
      Parallax Abstraction earned a badge
      Dedicated
    • First Post
      956400 earned a badge
      First Post
    • Week One Done
      davidfegan earned a badge
      Week One Done
  • Popular Contributors

    1. 1
      +primortal
      616
    2. 2
      ATLien_0
      227
    3. 3
      +FloatingFatMan
      170
    4. 4
      Michael Scrip
      166
    5. 5
      Som
      148
  • Tell a friend

    Love Neowin? Tell a friend!