Problem with KB905749 update

D

Don Burnette

I recently downloaded and installed the latest 9 updates available for
Windows XP. I have XP Pro, and have always kept it updated through windows
update.

After installing the above updates, I noticed my hardware listing in device
manager had disappeared. I tried the reg fix from Kelly's website, with no
luck. I ended up restoring an image of my C drive to get it back.

I then went through and installed the updates individually, to find out
which update was causing my problem. It was the kb905749 critical update. If
I download and install it, upon rebooting, all items listed in device
manager are gone, just a blank white screen. It also messes up my being able
to uninstall my video drivers to install newer ones.

Has anyone else run across this? The other 8 windows updates installed
without issue, it is just this one remaining update that messes up my
system. Anyone know of a work around?

I do disable my AVG Antivirus before downloading and installing the update.

Any help would be greatly appreciated.
 
O

Ottmar Freudenberger

Don Burnette said:
I then went through and installed the updates individually, to find out
which update was causing my problem. It was the kb905749 critical update. If
I download and install it, upon rebooting, all items listed in device
manager are gone, just a blank white screen. It also messes up my being able
to uninstall my video drivers to install newer ones.
Click to expand...

Any hints in the event viewer? Any service hanging or not starting?

Bye,
Freudi
 
D

Don Burnette

Ottmar said:
Any hints in the event viewer? Any service hanging or not starting?

Bye,
Freudi
Click to expand...


No, none that I see.

How I found out I had the problem, was I was trying to update my video
drivers a week or so ago, this was shortly after I had downloaded and
installed the 9 latest windows xp updates. I could not uninstall my video
drivers, nor install the new ones, I got an error that it could not be
initialized, the remote procedure call failed or something like that. Upon
looking further, I realized I had no hardware showing in my device manager,
just a blank white screen.
I restored my system to a previous image, and all was well.

After grabbing the updates again , same thing happened. I then realized it
must be one of the updates doing this, so I tried system restore and it
would not restore to any restore point I chose, so I restored the same image
again. I then went to windows update site and grabbed them individually,
until I found the one that was causing this - kb905749.

I perused through this newsgroup and did not see where anyone else had
posted for this kind of issue.
 
D

Don Burnette

Ottmar said:
The "Plug & Play" service is up and running?

Bye,
Freudi
Click to expand...


Yes, both before and after installing the update, plug and play service is
running.

Thanks,
 
O

Ottmar Freudenberger

Don Burnette said:
Yes, both before and after installing the update, plug and play service is
running.
Click to expand...

Hmpf, what's the version number of the umpnpmgr.dll?
Could you access device manager after booting into Windows XP's save mode?

Bye,
Freudi
 
D

Don Burnette

Ottmar said:
Hmpf, what's the version number of the umpnpmgr.dll?
Could you access device manager after booting into Windows XP's save
mode?

Bye,
Freudi
Click to expand...


I show 4 files named umpnpmgr.dll ( one of which is in a kb uninstall
folder )

There are two version numbers,

5.1.2600.2710
5.1.2600.2180

2710 is in c:windows\system32 folder .

No, even in safe mode, after installing kb905749, nothing shows up in device
manager.


Thanks,
 
O

Ottmar Freudenberger

Don Burnette said:
I show 4 files named umpnpmgr.dll ( one of which is in a kb uninstall
folder )

There are two version numbers,

5.1.2600.2710
5.1.2600.2180

2710 is in c:windows\system32 folder .
Click to expand...

Ooops, KB905749 should install version 5.1.2600.2744 dated 08-23-05.
Version 5.1.2600.2710 is the version which comes with KB899588 which
has been replaced by KB905749. Did you check the version number with
KB905749 installed? If so, any hints in the KB905749.log file to be
found in the Windows folder?
No, even in safe mode, after installing kb905749, nothing shows up in device
manager.
Click to expand...

Grmbl

Bye,
Freudi
 
D

Don Burnette

Ottmar said:
Ooops, KB905749 should install version 5.1.2600.2744 dated 08-23-05.
Version 5.1.2600.2710 is the version which comes with KB899588 which
has been replaced by KB905749. Did you check the version number with
KB905749 installed? If so, any hints in the KB905749.log file to be
found in the Windows folder?


Grmbl

Bye,
Freudi
Click to expand...


No, I currently do not have KB905749 installed, which is I guess why I have
the older version.
After installing 905749, I had to restore an image of my C partition, system
restore would not even work, could not restore to the previous restore
point.
This is twice I have had to restore from an image due to this issue, and I
really don't want to have to do it again, although I guess I could shut down
system restore then restart it in hopes that it will work the next time.
 
D

Don Burnette

Ottmar said:
Ooops, KB905749 should install version 5.1.2600.2744 dated 08-23-05.
Version 5.1.2600.2710 is the version which comes with KB899588 which
has been replaced by KB905749. Did you check the version number with
KB905749 installed? If so, any hints in the KB905749.log file to be
found in the Windows folder?


Grmbl

Bye,
Freudi
Click to expand...


Ok, I went ahead and disabled and re-enabled system restore, and created a
new image of my C partition if needed.

I downloaded and installed KB905749, and once again, nothing is showing in
device manager, just a blank white screen.

I now show 8 files named umpnpmgr.dll. The version of the one in the
windows/system32 folder is 5.1.2600.2744

I copied the first part of the log file ( not the complete log file), and it
appears it shows a problem with " installation did not complete". I have
included it below in case it gives any hints as to why it is doing this..

I will try to uninstall the hotfix first, and if that doesn't work, will try
the system restore point that was set.



[KB905749.log]
3.016:
================================================================================
3.016: 2005/10/23 17:46:14.828 (local)
3.016:
C:\WINDOWS\SoftwareDistribution\Download\S-1-5-18\a10059c9324422cfcb0f7ef897dbfc6d\update\update.exe
(version 6.1.22.4)
3.031: Hotfix started with following command line: /si
/ParentInfo:8e0af7288a03b845bdc6e142a5e02ed9
4.656: DoInstallation: CleanPFR failed: 0x2
4.688: SetProductTypes: InfProductBuildType=BuildType.IP
4.688: SetAltOsLoaderPath: No section uses DirId 65701; done.
4.735: CreateUninstall = 1,Directory = C:\WINDOWS\$NtUninstallKB905749$
4.735: LoadFileQueues: UpdSpGetSourceFileLocation for halaacpi.dll failed:
0xe0000102
4.766: ref tag c:\windows\system32\sp4.cab does not exist
4.766: ref tag c:\windows\system32\sp3.cab does not exist
4.766: ref tag c:\windows\system32\sp2.cab does not exist
4.766: ref tag c:\windows\system32\sp1.cab does not exist
4.766: ref tag c:\windows\system32\driver.cab does not exist
4.766: ref tag c:\windows\system32\fp40ext.cab does not exist
4.766: ref tag c:\windows\system32\fp40ext1.cab does not exist
4.766: ref tag c:\windows\system32\wms4.cab does not exist
4.766: ref tag c:\windows\system32\wms41.cab does not exist
4.766: ref tag c:\windows\system32\ims.cab does not exist
4.766: ref tag c:\windows\system32\ims1.cab does not exist
4.766: ref tag c:\windows\system32\ins.cab does not exist
4.766: ref tag c:\windows\system32\ins1.cab does not exist
4.781: Starting AnalyzeComponents
4.781: AnalyzePhaseZero used 0 ticks
4.781: No c:\windows\INF\updtblk.inf file.
4.781: OEM file scan used 0 ticks
4.797: AnalyzePhaseOne: used 16 ticks
4.797: AnalyzeComponents: Hotpatch analysis disabled; skipping.
4.797: AnalyzeComponents: Hotpatching is disabled.
4.797: FindFirstFile c:\windows\$hf_mig$\*.*
6.031: AnalyzeForBranching used 31 ticks.
6.031: AnalyzePhaseTwo used 0 ticks
6.031: AnalyzePhaseThree used 0 ticks
6.141: AnalyzePhaseFive used 110 ticks
6.141: AnalyzePhaseSix used 0 ticks
6.141: AnalyzeComponents used 1360 ticks
6.141: Downloading 2 files
6.141: bPatchMode = TRUE
6.141: Inventory complete: ReturnStatus=0, 1406 ticks
6.141: Num Ticks for invent : 1406
6.172: [dumpDownloadTask] Update.exe posting request file to download a
total of 47636 bytes (47636 bytes in patches and 0 bytes in fallbacks)
6.172: dumpDownloadTask returned 0xf200 (more files to download)
6.188: KB905749 installation did not complete.
6.188: Update.exe extended error code = 0xf200
0.531:
================================================================================
0.531: 2005/10/23 17:46:19.578 (local)
0.531:
C:\WINDOWS\SoftwareDistribution\Download\S-1-5-18\a10059c9324422cfcb0f7ef897dbfc6d\update\update.exe
(version 6.1.22.4)
0.531: Hotfix started with following command line: /si
/ParentInfo:5ffe4a27ed90db41a30250bb0249f1a0
0.968: DoInstallation: CleanPFR failed: 0x2
0.968: SetProductTypes: InfProductBuildType=BuildType.IP
0.968: SetAltOsLoaderPath: No section uses DirId 65701; done.
0.984: Express: 47,636 bytes were downloaded.
1.000: [PatchFilesFromResponseBlob] returning STATUS_READY_TO_INSTALL
1.000: KB905749 installation did not complete.
1.000: Update.exe extended error code = 0xf201


0.750:
================================================================================
0.750: 2005/10/23 17:46:24.578 (local)
0.750:
C:\WINDOWS\SoftwareDistribution\Download\843953281f8497f8e20b19c4e3fe3e01\update\update.exe
(version 6.1.22.4)
0.750: Failed To Enable SE_SHUTDOWN_PRIVILEGE
0.765: Hotfix started with following command line: -q -z -er
/ParentInfo:b2611c4a8468bb4f83a48faf4ae29e6e
1.250: In Function TestVolatileFlag, line 11660, RegOpenKeyEx failed with
error 0x2
1.250: In Function TestVolatileFlag, line 11692, RegOpenKeyEx failed with
error 0x2
1.250: DoInstallation: CleanPFR failed: 0x2
1.265: SetProductTypes: InfProductBuildType=BuildType.IP
1.265: SetAltOsLoaderPath: No section uses DirId 65701; done.
1.281: CreateUninstall = 1,Directory = C:\WINDOWS\$NtUninstallKB905749$
1.281: LoadFileQueues: UpdSpGetSourceFileLocation for halaacpi.dll failed:
0xe0000102
1.281: ref tag c:\windows\system32\sp4.cab does not exist
1.281: ref tag c:\windows\system32\sp3.cab does not exist
1.281: ref tag c:\windows\system32\sp2.cab does not exist
1.281: ref tag c:\windows\system32\sp1.cab does not exist
1.281: ref tag c:\windows\system32\driver.cab does not exist
1.281: ref tag c:\windows\system32\fp40ext.cab does not exist
1.281: ref tag c:\windows\system32\fp40ext1.cab does not exist
1.281: ref tag c:\windows\system32\wms4.cab does not exist
1.281: ref tag c:\windows\system32\wms41.cab does not exist
1.281: ref tag c:\windows\system32\ims.cab does not exist
1.281: ref tag c:\windows\system32\ims1.cab does not exist
1.297: ref tag c:\windows\system32\ins.cab does not exist
1.297: ref tag c:\windows\system32\ins1.cab does not exist
1.297: Starting AnalyzeComponents
1.297: AnalyzePhaseZero used 0 ticks
1.297: No c:\windows\INF\updtblk.inf file.
1.297: OEM file scan used 0 ticks
1.297: AnalyzePhaseOne: used 0 ticks
1.297: AnalyzeComponents: Hotpatch analysis disabled; skipping.
1.297: AnalyzeComponents: Hotpatching is disabled.
1.297: FindFirstFile c:\windows\$hf_mig$\*.*
1.312: AnalyzeForBranching used 0 ticks.
1.312: AnalyzePhaseTwo used 0 ticks
1.312: AnalyzePhaseThree used 0 ticks
1.312: AnalyzePhaseFive used 0 ticks
1.312: AnalyzePhaseSix used 0 ticks
1.312: AnalyzeComponents used 15 ticks
1.312: Downloading 0 files
1.312: bPatchMode = TRUE
1.312: Inventory complete: ReturnStatus=0, 31 ticks
1.312: Num Ticks for invent : 31
1.312: VerifySize: Unable to verify size: Source = NULL:
c:\windows\inf\HFX6A.tmp
1.344: Copied file: c:\windows\inf\branches.inf
2.265: Allocation size of drive C: is 4096 bytes, free space = 5147443200
bytes
2.297: AnalyzeDiskUsage: Skipping EstimateDiskUsageForUninstall.
2.297: Drive C: free 4908MB req: 10MB w/uninstall: NOT CALCULATED.
2.297: CabinetBuild complete
2.297: Num Ticks for Cabinet build : 985
2.297: DynamicStrings section not defined or empty.
2.297: FileInUse:: need to restart already, turn off
3.297: LoadFileQueues: UpdSpGetSourceFileLocation for halaacpi.dll failed:
0xe0000102
3.375: Num Ticks for Backup : 1078
3.422: Num Ticks for creating uninst inf : 47
3.422: Registering Uninstall Program for -> KB905749, KB905749 , 0x0
3.422: LoadFileQueues: UpdSpGetSourceFileLocation for halaacpi.dll failed:
0xe0000102
3.422: System Restore Point set.
3.484: Copied file: C:\WINDOWS\system32\spmsg.dll
3.500: PFE2: Not avoiding Per File Exceptions.
 
D

Don Burnette

I was able to remove the KB905749 update through add/remove programs, and
upon rebooting my device manager is back.

Wierd, I am suprised no one else is seeing this issue...
 
O

Ottmar Freudenberger

Don Burnette said:
I downloaded and installed KB905749, and once again, nothing is showing in
device manager, just a blank white screen.

I now show 8 files named umpnpmgr.dll. The version of the one in the
windows/system32 folder is 5.1.2600.2744
Click to expand...

Okay.

Have a look onto http://www.annoyances.org/exec/forum/winxp/t1051715405
and especially into the HKLM\System\CurrentControlSet\Enum folder in the
registry and it's permissions. Is "System" listet there too?

Bye,
Freu"Found nothing unusual in the LOG file"di
 
D

Don Burnette

Ottmar said:
Okay.

Have a look onto
http://www.annoyances.org/exec/forum/winxp/t1051715405 and especially
into the HKLM\System\CurrentControlSet\Enum folder in the registry
and it's permissions. Is "System" listet there too?

Bye,
Freu"Found nothing unusual in the LOG file"di
Click to expand...


I have verified, plug and play service is running, and System has full
permissions in the enum folder.

Thanks for trying to help, any other ideas?
This is really baffling.
For whatever reason, KB905749 update really messes up my device manager...
 
O

Ottmar Freudenberger

Don Burnette said:
I have verified, plug and play service is running, and System has full
permissions in the enum folder.
Click to expand...

Hmpf, so I'm out of the game, assuming, that a "regsvr32 ole32.dll"
doesn't help either.

Bye,
Freudi
 
M

Michael Jennings

Search kb905749 in google shows others with identical problems.

Microsoft has got to be working on why it does this because they
need to incorporate the fix in sp3 for XP. I append 'get to support.'
"On Windows XP Service Pack 2, this is strictly a local privilege
elevation vulnerability," so I guess that if you have no really smart
black hat cleaning people, you don't really need 905749.

Don Burnette said:
I have verified, plug and play service is running, and System has full
permissions in the enum folder.

Thanks for trying to help, any other ideas?
This is really baffling.
For whatever reason, KB905749 update really messes up my device manager...
Click to expand...
In Internet Explorer click on help > then Online Support >
In the Assisted Support section, click on >
Select a product to view your assisted support options
In the Windows section click on > Windows Update
Select a language and click the arrow >
 
P

Plato

Don said:
I then went through and installed the updates individually, to find out
which update was causing my problem. It was the kb905749 critical update. If
Click to expand...

I went out to eat once a a new place. Found out I didn't agree with a
certain food. So, I dont try that food anymore.
 
G

Guest

Don,

Thanks for your hard work and respect for the community by continuing to
post on this topic.

I too discovered I hand an empty device manager recently. I was trying to
install new keyboard drivers and got a similar error as you did on your video
driver update.

I uninstalled the KB905749 update through Control Panel /uninstal software /
(enable viewing of updates) and highlighted it and removed it.
It came up with about 8 or so (estimate) other updates that it said would go
with it. I let them go too and rebooted.

Right away I went in and now can see my device manager contents.

I have updates waiting to be installed already (auto update ya know) and
from what you've reported so far, I'll bet even money after the update my
device manager gets tagged again.

Anyway, thanks for the info
 
D

Don Burnette

Glad to help.

While I hate that it happened to you, at least I know someone else here has
had the same problem.
I was able to uninstall it as well, however I do not recall getting a
message that others would be removed with it.

It would be nice to know what is causing it.

In the meantime, I am just going to stay away from KB905749...


Don Burnette
 

Ask a Question

Want to reply to this thread or ask your own question?

You'll need to choose a username for the site, which only take a couple of moments. After that, you can post your question and our members will help you out.

Ask a Question

Similar Threads

Conflict with security update KB905749 2
Strange Update 6
WIN XP - PATCH KB905749 - will not connect IPOD 1
Windows 10 Is it Safe to Disable Updates 13
KB905749 and Empty Device Manager 2
problem with Windows update 9
Windows 10 Windows update 2004 problem. 10
Xp update problems 4

Top