Windows 10: Logical Disk Manager

A group of uers in my firm have been issued new computers using winows 10. One user cannot access disk properties on their computer with error; “You do not have access rights to Logical Disk Manager on Windows 10 Professional Version.” Ongoing local security policies and tests might be a problem. If the local security policies are the issues then that's one case and if they are not the issue then that's a different case. How can I resolve the issue for these 2 cases?

:)

 

Unable to Connect to Logical Disk Manager Service Error in Computer Management

WELL, I'll be an "S.O.B."! I got it... lol, just now!

Apparently, & I am going to record this & BOOKMARK/FAV it in my webbrowsers as "HOW TO FIX LOGICAL DISK MANAGER HASSLES" (lol), it is SOMETHING in my services!

You need THIS list of them running (provided you have them online that is, some OS won't have SOME of these (this is Windows Server 2003) & some are 3rd party & won't matter):





* NO SAFE MODE REQUIRED - THIS FIXED IT, PURELY SERVICES RELATED... oddly, no "dependencies" other than the ones the services need (RPC & Plug n Play) are listed in the 2 services for Logical Disk Management... it's like MS missed (somehow) the fact that there IS other dependencies on other services than what they list!

That list above is PROBABLY "overkill" & it is only a fraction of that list above, but the point is there... with ALL of those active? Logical Disk Manager "gets its act together" again & works!

APK

P.S.=> BRB, with screenshot of services & their startup status needed for this to work, in case anyone else hits this... it is a real you-know-what if you can't get to a disk to format it, lol... so, recording it for everyone's sake! apk

 

Strange Issue with Logical Disk Manager...

If you are using XP, it will always assign it to the next logical letter immediately following your last local drive. (So if you have C:, D: and E:, it will assign it to F: )
It does this even if you have already mapped that letter (Duh to XP).
If you disconnect the mapped drive you will see the stick.
Go into disk manager and map the stick way out on the list (something like S: ) and then remap the drive it was hiding behind. When you reboot XP will always see the stick as S: from then on.
You will have to do this for every stick.

The other option is to move the originally mapped drive out farther and let XP use the next local drive for all the sticks and other USB devices. Then you will only need to do one remap.

 

Disk management console view is not up-to-date

i dont know how to fix your disk management, but i can fix your partition problems...




open up Command Prompt with admin rights. (Right click, run as admin)


enter in
DISKPART
list disk

then find the Disk number for your Raid array... lets call it number 7 ( you can tell what disk is what by the total size)
type in

Select Disk 7
List Partition (will give you a list of all the partitions..)
Select Partition 1 (im assuming you only have 1 partition on Disk 7) repeat this step if you have more partitions.
ASSIGN


that should get the array up and running ready to use.


EDITED.

any problems, post back ^^


Still EDITING *Stick Out Tongue

side question, have you tried restarting the PC?