On Microsoft Windows [Version 5.2.3790] system I am getting a crash.
It always appears with KB944338_xp_2k3_x64_enu.apm
Log ->
What AutoPatcher was trying to do
It appears that the error occured while AutoPatcher was trying to determine if a specific version of a file is present.
Where: mdlModuleLoading.isFileDetected()
Error Code: 0x80070714: Method '~' of object '~' failed
AutoPatcher 5.6 loaded the filesystem.
Detected English (1033) Service Pack 2
System Components:
Internet Explorer: 6.0.3790.4324
Windows Media Player: 11.0.5721.5230
.NET Framework: 2.0.50727.1433|2.0SP1|3.1.21022|3.1SP1|3.5|3.5SP0
Windows Installer: 3.1.4000.3959
DirectX: 4.09.00.0904
MSN/Live Messenger:
Office Components:
Microsoft Word: 12.0.6211.1000
Microsoft Excel: 12.0.6214.1000
Microsoft PowerPoint: 12.0.6211.1000
Microsoft Outlook: 12.0.6212.1000
Microsoft Access: 12.0.6211.1000
Microsoft Project:
Microsoft Publisher: 12.0.6211.1000
Microsoft OneNote: 12.0.6211.1000
Microsoft FrontPage:
Microsoft InfoPath: 12.0.6211.1000
Microsoft Visio:
Microsoft SharePoint Designer:
Microsoft Groove: 12.0.6211.1000
Any tips?
1
Autopatcher XP x64 crash Yikes!
Started by Guest_viiru_*, Jan 04 2009 06:31 PM
1 reply to this topic
#2
-
- Veterans
-
- 3,851 posts
Super Helpful Guy
- Gender:Male
- Location:Brazil (Santa Maria - RS)
Posted 04 January 2009 - 07:34 PM
> It appears that the error occured while AutoPatcher was trying to determine if a specific version of a file is present
you are right. several softwares have the exact same issue when need detect something into another file. i don't know for sure an permanent fix for the issue that isn't change the detection parameter on the module or change certain parameters into autopatcher.exe to try bypass the issue. i too don't know if someone is still holding the x64 versions, but if you are sure that is this the module giving you trouble, you can:
- remove the apm file related to the module and install the kb by hand;
- check for the file pointed into the .apm file, learn another detection and edit the file to remove that detection
[]s
you are right. several softwares have the exact same issue when need detect something into another file. i don't know for sure an permanent fix for the issue that isn't change the detection parameter on the module or change certain parameters into autopatcher.exe to try bypass the issue. i too don't know if someone is still holding the x64 versions, but if you are sure that is this the module giving you trouble, you can:
- remove the apm file related to the module and install the kb by hand;
- check for the file pointed into the .apm file, learn another detection and edit the file to remove that detection
[]s
2 user(s) are reading this topic
0 members, 2 guests, 0 anonymous users
