Logical Disk Manager Administrative Service set to Manual (and
default is not started)
Logical Disk Manager set to Automatic (and started)
ps. apperantly am not the only one having this problem:
http://www.mcse.ms/message469603.html
![[H]ard|Forum](/styles/hardforum/xenforo/logo_dark.png){kind=logo}
[WinXP] Disk Management errors out
- Thread starter ashrack
- Start date
Logical Disk Manager Administrative Service set to Manual (and
default is not started)
Logical Disk Manager set to Automatic (and started)
ps. apperantly am not the only one having this problem:
http://www.mcse.ms/message469603.html
Since it works in safe mode, your best bet is to try removing the items in normal mode to the best approximation of safe mode you can make in regular mode.
If it works at that point begin adding items back until you lose functionality. Then you have identified your culprit. Of course, part of safe mode is limiting DCOM to MS only OS items...
I ened up having s imilar issue with DCOM that was keeping my backups from working as the volume shadow copy service couldn't initialize. Turned out to be caused by installing an old graphics software program, Micrografx Picture Publisher 10. It hooked into DCOM in a way that was not allowed under XP SP2. I installed a patch for the software, and my problem was resolved.
You don't even want to know how long it took me to find it. Or what I ended up going through...
Several months of looking at it occasionally for a few hours each week, I finally bit the bullet.
I ended up installing a new copy of XP on a second drive, then installing everything in my regular build 3 apps at a time until it broke, then removing those one at a time until it started working again. You could have floored me when I uninstalled a graphics app and my backups started working again.
I was lucky to find the patch as the app had been sold twice, and the latest owner no longer hosted the patches. I found an individual still hosting the patches. There was no documentation in the patch about it addressing anything like the issue I was experiencing, but it resolved it. Wrote the guy hosting the patches a very heartfelt thank you note.
If it works at that point begin adding items back until you lose functionality. Then you have identified your culprit. Of course, part of safe mode is limiting DCOM to MS only OS items...
I ened up having s imilar issue with DCOM that was keeping my backups from working as the volume shadow copy service couldn't initialize. Turned out to be caused by installing an old graphics software program, Micrografx Picture Publisher 10. It hooked into DCOM in a way that was not allowed under XP SP2. I installed a patch for the software, and my problem was resolved.
You don't even want to know how long it took me to find it. Or what I ended up going through...
Several months of looking at it occasionally for a few hours each week, I finally bit the bullet.
I ended up installing a new copy of XP on a second drive, then installing everything in my regular build 3 apps at a time until it broke, then removing those one at a time until it started working again. You could have floored me when I uninstalled a graphics app and my backups started working again.
I was lucky to find the patch as the app had been sold twice, and the latest owner no longer hosted the patches. I found an individual still hosting the patches. There was no documentation in the patch about it addressing anything like the issue I was experiencing, but it resolved it. Wrote the guy hosting the patches a very heartfelt thank you note.