AutoPatcher Bug Reports

[dragon25]

well im gutted, its the first time ive used ap and actually had my system run the worst it ever been .

3 days after installing from the nov full package and dec up and jan update its been real slow on the start up specifically, and ive minized the startup apps to just sound and firewall which is zonelabs security suite.

but saying that i just tried not running the firewall and its the same thing, so im going to unsiatll ap all together get updates from MS and only install a few thigns from ap. im simply gutted

[djg05]

I have only recently come across this site and d/l the patch (AutoPatcher_2000_Nov06_ENU_Full.exe) for Windows 2k. I tried updating my system with the default options and about a third of the way in I had a BSOD. On rebooting I found that Windows had to do a dskchk on all my partitions which is very unusual.

I tried again this time removing all options for IE which I do not use. Also unchecked the DRM (?) options. Same thing happened again.

Is there a work around for this please.

[PsiMoon314]

Hi Angelico_Payne,

As regards the IE7 installation issues please take a look at your %windir%\ie7.log and %windir%\ie7_main.log files to see why the installation appears to have failed.

If your copy of AP is running the IE7 installation in passive mode then you should see something on screen during the IE7 install which might indicate what is causing the issue.

Please remember that you do need to activate and validate your copy of Windows XP before IE7 will install. If you have not done this with your clean installation of XP then IE7 will generally not install.

WMP11 always want to validate before you can use it for the first time, expecially on a new Windows XP installation. Clearly you always want to install windows with a valid product key and activate before you install software which requires online activation.

However I have found the WMP11 installer to be quite relaxed about installing even on unvalidated XP installs however you do need to validate the OS and WMP11 before you can use it.

Check %windir%\wmp11.log for the full installation report for your copy of WMP11.

After installing numerious hotfixes and patches your system registry files will probably be badly fragmented. Please visit

http://www.microsoft.com/technet/sysintern...PageDefrag.mspx

and download PageDefrag to defragment these files. Using a seperate tool to defgarment the rest of the drive might not be the worst idea either to improve system performance :)

Does your XP system have at least 512 MBytes of RAM installed?

Anything less will probably feel sluggish expecially with antivirus software running or if the system takes part of main memory for the graphics system (onboard or integrated graphics).

Kind Regards

Simon

[WhatWarning]

When running AutoPatcherXP on a clean install of Windows XP Media Center Edition 2005 with Service Pack 2, the Internet Explorer 7 icon on the Start Menu changes to an unknown icon. Please note I have tested this same version of AutoPatcherXP(January Edition) on the same computer running Windows XP Professional Service Pack 2 and the problem does not occur.

The solution I found for Media Center PC's is:

1) Install everything from Microsoft Update/Windows Update and go back to AutoPatcher and install the tweaks only.

[ngp]

AutoPatcher XP, even as of the most recent up-to-date Full release, doesn't appear to include Adaptec ASPI in the Addons section even though it's listed on the web site as one of the things supposedly included.

[rsrcomp]

Blaze, did you remove .NET 2.0. Using Feb 07 and it does not load. I know NET 3.0 includes it but many apps look for ver 2.0 and it shows up in the Microsoft updates.

Just my 2 cents worth.

p.s. You must be a work-a-holic for the all the work you do.

[glutton4sw]

On running AP i get a windows error message box displayed "incorrect command line param...." AP then continues to install the other selected updates. The error box appears early on around the 4th update being installed. iv'e done clean installs a few times and its the same message i get. my system setup:

clean install of windows 2000 with sp4 slipstreamed

install AP Aug06 full then all the updates to Feb07

run AP and select just internet explorer 6 sp1 to install

on the next run of AP i install all other updates ie critical and non-critical i get a "incorrect command line param.." message box appear just the once.

the only other issue i have is that some updates don't install as prerequisites are not met..kb926121,kb926247 but there are one or two others.

is this just unique to my system?

hopefully the next ap release with new engine will remove the above problem.

[glutton4sw]

just done a clean install and got the same message box on running AP...incorrect command line param reported by windows installer v2

the modules that didnt install are:

Critical Update KB926121 Security Update for Windows 2000 - prerequisite failed (as expected)

Critical Update KB926247 security update for windows 2000 - prerequisite failed (as expected)

Updated Component KB823490 MSXML 2.6

Updated Component KB887606 MSXML 2.6

updates ive found not in AP (up to Feb07):

Windows-KB890830-V1.27.exe

Windows2000-KB923689-x86-ENU.EXE

Windows2000-KB931836-x86-ENU.exe

[abraham1]

Hello

The Remove Shortcut arrow tweak made it impossible for my Hauppauge pvr350 to startup TV via the remote. Undo-ing this tweak revived my IR.

Just thougth i'd let you guys know

[lordwiki]

What AutoPatcher was trying to do

It appears that the error occured while AutoPatcher was trying to set folder variables through filesystem.

Where: mdlInitialization.Main()

Error Code: 0x153: Component 'MSCOMCTL.OCX' or one of its dependencies not correctly registered: a file is missing or invalid

[smith0166]

Hi,

I have a wierd problem...

I cannot run editor.exe (the module editor)

I CAN run AutoPatcher.exe, Module Installer.exe, Hotfix Cleaner.exe and the old Tweak Undo.exe

Can anyone please confirm the MD5 hash for editor.exe. Mine is 113205689919A338B4816AACCF7CACDF. And also the Hash for the OCX & DLL files in the autopatcher\BIN directory.

I had the same problem with autopatcher Nov 2006 and all the updates to Feb 2007.

I thought that the new release would fix it, but it has not.

I have copied all the OCX & DLL files from the autopatcher\BIN directory to the windows\system32 directory an re-registered them. All the above program files EXCEPT Editor.exe.

I have copied COMDLG32.OCX file from the tools\BIN directory to the windows\system32 directory an re-registered it. All the above program files EXCEPT Editor.exe.

I have unregistered the OCX & DLL files and re-registered them from the autopatcher\BIN directory. All the above program files EXCEPT Editor.exe.

I have unregistered COMDLG32.OCX file and re-registered it from the tools\BIN directory. All the above program files EXCEPT Editor.exe.

Any help would be much appreciated.

S

[frob27]

AutoPatcher XP May 2007

On one machine I get "Run time error 429 - activeX component can't create object!" when I run the Hotfix Cleaner Tool.

After 2-3 hours of searching the web, dicking around registering DLLs and OCXes it turns out I needed to install and register REGOBJ.DLL which I assume should be but isn't part of the autopatcher install.

Trust Microsoft to come up with such a completely useless error message for a simple problem with a simple fix if only they would tell you what the problem was. 19,000 hits on google for this error message and probably several hundred solutions to the different problems which all give the same error message.

Another minor issue, a start menu shortcut points to "Module Editor.exe" but autopatcher installs "editor.exe".

[glutton4sw]

@smith0166 try adding "C:\Program Files\AutoPatcher 2K\bin" to the start of the PATH environment variable. the path given is for windows 2000, other versions of AP will be different. i think AP installs OCX and DDLs to its own folder so its portable from one machine to another. let me know if it works!

[smith0166]

@smith0166 try adding "C:\Program Files\AutoPatcher 2K\bin" to the start of the PATH environment variable. the path given is for windows 2000, other versions of AP will be different. i think AP installs OCX and DDLs to its own folder so its portable from one machine to another. let me know if it works!

That did not do it...

Actually, when I tried that, the progs (Hotfix Cleaner.exe, Tweak Undo.exe & editor.exe) would not run. Then when I rebooted the computer, they began to run again.

I still have the directory in the start of PATH.

I think I may have a DLL/OCX that is not compatible.

Any chance that theblazingangel can give me a list of ALL the libraries that are being used and their MD5 hashes so that I can check.

TIA

S

[ckit]

When exiting AutoPatcher 2000 May 2007,

I get these error messages under Windows 2000 Pro SP4.

[supermouse]

last night, i was searching for troubles on my translated version and i've found an invalid install string at KB891122. it wasn't running them i try run it by command line without that /quiet option, choosing the remain install format and i think that i may have found the problem. original install string is this:

"Module:\WindowsMedia-KB891122-x86-PTB.exe" /quiet /norestart /DisallowSystemRestore

(of course, to run it at command line, i've changed to WindowsMedia-KB891122-x86-PTB.exe /norestart /DisallowSystemRestore ). then, i've got something like this:

http://xs216.xs.to/xs216/07231/kb891122.gif

removing that /DisallowSystemRestore it gives another message, about already be included in SDK or something, but this last message may have be due something that i've installed previously. you may reply this in a english version of AP, like i did

minor issue, anyway

[]s

[glutton4sw]

@supermouse KB891122 in AP W2K 5.1 install is

"AutoPatcher:\Modules\NonCritical\KB891122_2k\WindowsMedia9-KB891122-x86-Global-ENU.exe" /quiet /norestart /overwriteoem

and without backups:

"AutoPatcher:\Modules\NonCritical\KB891122_2k\WindowsMedia9-KB891122-x86-Global-ENU.exe" /quiet /norestart /nobackup /overwriteoem

i have the AP W2K May installed too but im unable to open AP May07 (v5.6) modules using the editor..it will only open AP 5.1 module files. editor.exe is dated 12 March 2007 so it looks like its not been updated for the AP May release.

[supermouse]

glutton4sw, thanks. that module should be ok now, but will test it again later. i've added a few missing modules in here too, in order to allow user keep out ie7 and wmp, if he wish. the modules that i've added are: KB890046 and 924496. i've already had KB925720 in my last beta, but seems that is missing in english, so, i've added it again. i've added again CmdHere_Powertoy_xp_x86_ptb.apm on Extras package, with the others powertoys.

about module editor, the last one made public is 2.0.0.9, that is on AP english core release, but will not works with .apm files. the last AP exe that i have is the one that comes with AP english core release, that is 5.6.0.72. i was thinking that i was miss editor, but i've don't. i miss a few things, but notepad works better.

by the way: so far, i had to remove a few modules in wmp10 package. by some reason, a lot of those kb are english only and despide ms say that are international, they aren't and does not install in some languages. so far are out: KB894395, KB896344, KB912461, KB923800, KB927544, KB924732 and a few other ones are in test yet

[arffer]

AutopatcherXPCore June 2007

Configuration:

XP Pro SP2 autopatched up thru March 2007

Two physical drives:

SATA Drive C: with Windows and applications

PATA Drive D: only stored data

I just ran the new June 2007 XPCore Autopatcher. Upon reboot, the error "windows\system32\config\system" appears.

I entered the recovery console off of the CD, and was rather surprised to find that the console was showing that my Windows install was now showing as being on the "D:" drive, not "C:".

I switched over to C: after logging into the console, and a DIR showed that "C:" was now my data storage drive.

Now, it is important to note that there are NO Windows system files on the data storage drive, and NO MBR on that drive. In fact, if I disconnect the SATA drive and configure my BIOS to try and boot off of the data storage drive, I get the expected "missing operating system" error.

So, it seems apparent that XP is initially booting off of my SATA boot drive, but very early in the boot process, the drive letters switch, so when XP tries to read the SYSTEM hive from "C:\windows\system32\config\system" it can't, because it is by then trying to read from the wrong physical drive.

As a test, I physically disconnected the PATA data storage disk and booted again. The theory is that with only one drive attached, no drive letter switch could occur. Sure enough, Windows booted right up just fine.

After entering Windows with a single drive, I ran the drive manager, verified that drive was assigned to "C:", and exited. I then shut down, reattached the second data storage drive, and rebooted. The problem was gone, and XP booted just fine.

So, any ideas as to why the drive letters switched during the boot after I ran the new autopatcher? All help is appreciated!

-Alan

Edited June 4, 2007 by arffer

[PsiMoon314]

Hi,

i have the AP W2K May installed too but im unable to open AP May07 (v5.6) modules using the editor..it will only open AP 5.1 module files. editor.exe is dated 12 March 2007 so it looks like its not been updated for the AP May release.

Try using a text editor like Notepad or Wordpad to edit the AP 5.6 module files.

Kind Regards

Simon

[OldFawkz]

[snip]

So, it seems apparent that XP is initially booting off of my SATA boot drive, but very early in the boot process, the drive letters switch, so when XP tries to read the SYSTEM hive from "C:\windows\system32\config\system" it can't, because it is by then trying to read from the wrong physical drive.

As a test, I physically disconnected the PATA data storage disk and booted again. The theory is that with only one drive attached, no drive letter switch could occur. Sure enough, Windows booted right up just fine.

After entering Windows with a single drive, I ran the drive manager, verified that drive was assigned to "C:", and exited. I then shut down, reattached the second data storage drive, and rebooted. The problem was gone, and XP booted just fine.

So, any ideas as to why the drive letters switched during the boot after I ran the new autopatcher? All help is appreciated!

-Alan

I feel a bit nervous giving advice amongst people who know way more than I ever will, but here goes.....

Although I'm not sure how it might have been happening, there is one cause I'd look at first off. Windows XP doesn't recognize drives only by letter; it also stores a serial number (at random) on the disk itself. What that means is, a disk can be used, wiped, overwritten -- and Windows will still remember what letters that drive and its partitions used to be allocated. That can cause problems in some cases, if Windows suddenly takes it into mind that some essential file or data is on a drive that you aren't using for the system. This often kicks in midway through Windows startup, when it's figuring out drive related matters and loading files left right and centre. Formatting or redeploying a disk doesnt change the siggy.

One simple solution that solves most cases of this kind is this:

Create an MSDOS boot floppy, find some DOS based disk/mbr editor, and put it on the floppy.

Power down.

Disconnect all drives . (Yes, all of them)

For <i> = 1 to <number of disks>

Connect drive <i> alone

Power up on the MSDOS boot floppy.

Run said disk/MBR editor and use it to overwrite the 4 byte serial on the current hard drive

Power down.

Disconnect drive <i>

Repeat loop until all drives have had the serial overwritten

Result: All drives now have Windows serial ID's that don't match anything in Windows' list of "known drives"

Now.....

Power on the machine with just your main system drive alone. Not having a recognized serial, and being the sole drive, Windows will handle it correctly as drive C. Power down, then reboot, sure it's reliably working and identifying that drive as the system disk...

Then add back your other drives. The drive letters will all need reallocating correctly in Disk Manager, but since the serials have all been scrambled, Windows booting off your disk C won't be tempted to ID any of them as anything other than "extra data drives", and won't look for system data on them.

Necessary ingredients:

1) a DOS based MBR or Disk editor which can be used to edit the serial number on a hard drive.

2) 3 minutes googling to figure out which are the 4 bytes used for the drive siggy on an MBR disk.

Hope that helps, I don't know if that was your problem, but situations where the boot system is looking for data on some other disk, and if the other disk isn't present that works fine, do make me think of this situation.

[arffer]

One simple solution that solves most cases of this kind is this:

Thanks for the possible explaination and the solution :)

However, as I tried to explain in my post, after I sucessfully booted with just my single system drive connected, ran drive manager to confirm the assigned drive letter, and then shut down and reconnected both drives, the system came up fine.

So, I no longer have this problem, as it seems after entering and exiting drive manager, the system knew which drive should stay as "C:".

My post was more of one of wondering what one or more of the patches could have caused this. Also, I wanted to post incase anyone else had this situation, they could see how to correct it. But mostly wonder how it happened during the patching process.

Thanks!

[thejynxed]

AutoPatcher XP May 2007

On one machine I get "Run time error 429 - activeX component can't create object!" when I run the Hotfix Cleaner Tool.

After 2-3 hours of searching the web, dicking around registering DLLs and OCXes it turns out I needed to install and register REGOBJ.DLL which I assume should be but isn't part of the autopatcher install.

Trust Microsoft to come up with such a completely useless error message for a simple problem with a simple fix if only they would tell you what the problem was. 19,000 hits on google for this error message and probably several hundred solutions to the different problems which all give the same error message.

I've noticed the same thing. To save the troubles for anyone else running into this, here is what you do to fix it:

1) Download this: http://download.microsoft.com/download/vb6...-us/regobji.exe

2) Run the installer, and when it asks what directory to install in, you install it to: C:\Windows\System (or whatever drive letter your Windows install is on, and for Win2k, you would use C:\WINNT\System)

3) Go to Start > Run

4) In the Run box, type regsvr32 "C:\Windows\System\regobj.dll"

5) Yes you must include the quotations, and yes, the C:\Windows part will vary depending on if you use a different drive letter (or if you use Win2k, it would say WINNT instead of Windows)

6) Voila.

This file should have been part of and installed by the VBRUN60SP6.EXE included in the win9xnt folder, but for some reason, MS forgot to include it inside of the installer, OOPS.

[supermouse]

i've finished some tests right now. at instalation of windows defender (just 5 updates at that time) AP gone near to 100% cpu and stay in there for at least 10 minutes. after that, i've ended it and reboot. everything fine, but i've already saw this since the first version of ap 5.6 gone public. it's pretty rare, but...

at installation of wmp10 and 11, if you have disabled system restore, you got a warning about it. until you check that, it doesn't go away.

KB896097 and KB895316 does not install due language issues. KB921108 is already included in Windows Media SDK, so, if you install that first, you will not be able to install this one.

kb891122 and kb902344 fits for wmp9 too, but module need be edited in order to allow that. kb917734 have a version for wmp9 too, but if included, the wmp10 version may shows also uninstalled even if finish right. the .cat file of that kb doesn't replace the one from wmp9 that have the exact same name. it's possible bypass this by doing a detection by reg and by file. at least, i did that and it worked. of course, wmp9 version isn't on package, but i've added that in order to allow user stay out of wmp10 or 11.

after a dozen of reboots, a few kbs remains without uninstall. the guilty ones are this ones: 886903, 934238 (isn't on ap package, but it is an update from may according windows update. the only part of this that have uninstall is the lang pack. but ms did a test kb, so why it should have an uninstall?), 890830, 892211 (seems not have an uninstall), 934268 (it worked with MsiExec.exe /X{A43BF6A5-D5F0-4AAA-BF41-65995063EC44} ), wmp10 didn't roll over back to wmp9 after wmp11 roll over to 10, messenger 5.1, 917275 (it worked with MsiExec.exe /X{85E0BA25-A5DE-4499-82C2-B4CE4F513E80} ) and .net 3 (it just worked manually). some of this issues with uninstall may be related with system restore be disabled, i'm not sure, but i'm tired now to try again

[]s

[major4579]

I hope this is the correct place to post this - it's a non-important bug.

In Autopatcher 2000 (v5.6.73) when an item has subitems and all the subitems are marked as installed (blue) the item itself is still marked as NOT installed, it shows as black, should't it show as blue?

For example:

[-].....Microsoft Windows - Updated Components

.....[-].....MDAC (shows as Black)

...............Microsoft Data Access Components 2.8 SP1 (shows as Blue)

...............Security Update for MDAC 2.8 SP1 (shows as Blue)

It's not a big deal but I do need to expand items to see if they have all the subitems installed or not.

Thanks,

John