Disk Management Console view is not up-to-date.

Anonymous
2009-10-24T18:44:59+00:00

OS Name Microsoft® Windows Vista™ Ultimate

Version 6.0.6002 Service Pack 2 Build 6002

Other OS Description Not Available

OS Manufacturer Microsoft Corporation

System Name -----

System Manufacturer INTEL_

System Model DP45SG

System Type X86-based PC

Processor Intel(R) Core(TM)2 Quad CPU    Q6700  @ 2.66GHz, 2660 Mhz, 4 Core(s), 4 Logical Processor(s)

BIOS Version/Date Intel Corp. SGP4510H.86A.0083.2008.0819.1026, 8/19/2008

SMBIOS Version 2.4

Windows Directory C:\Windows

System Directory C:\Windows\system32

Boot Device \Device\HarddiskVolume1

Locale United States

Hardware Abstraction Layer Version = "6.0.6002.18005"

User Name -----

Time Zone Eastern Daylight Time

Installed Physical Memory (RAM) 2.00 GB

Total Physical Memory 2.00 GB

Available Physical Memory 691 MB

Total Virtual Memory 4.23 GB

Available Virtual Memory 2.38 GB

Page File Space 2.29 GB

Page File C:\pagefile.sys

Partition **** Disk #0, Partition #0

Partition Size **** 104.43 GB (112,134,193,664 bytes)

Partition Starting Offset 1,048,576 bytes

Partition **** Disk #0, Partition #1

Partition Size **** 361.33 GB (387,979,805,696 bytes)

Partition Starting Offset 112,133,668,864 bytes

I went to do something with partition magic (it recognized something with the pointers I believe, so I allowed it to automatically fix the error) and now I'm not even able to access Partition Disk #0, Partition #1 which is a drive that I used to store data (No OS).  It doesn't appear in 'My Computer', but does appear in Disk Management but it doesn't seem like I can do anything with it besides delete the partition.  There's a lot of data that I have stored and I don't want to lose it all.

I used a partition tool to find out what sectors each of the partitions are starting at and for one of them it's sector 15 and the other it is sector 33.  I'm not sure if that has any significance to my problem, but just thought I'd let it be known.

  • Program: Disk Managemet
  • Error Message: "The operation failed to complete because the Disk Management console view is not up-to-date.  Refresh the view by using the refresh task.  If the problem persists close the Disk Management console, then restart Disk Management or restart the computer.
Windows for home | Previous Windows versions | Performance and system failures

Locked Question. This question was migrated from the Microsoft Support Community. You can vote on whether it's helpful, but you can't add comments or replies or follow the question.

0 comments No comments
Answer accepted by question author
Anonymous
2010-01-25T12:43:17+00:00

I solved this problem by going into device manager and uninstalling the usb drivers. Then when I plugged the hard drive back in it reinstalled the driver and worked.

Was this answer helpful?

300+ people found this answer helpful.
0 comments No comments
Answer accepted by question author
Anonymous
2009-11-07T15:01:11+00:00

Hello trichard13,

Thank you for visiting the Microsoft Answers Community.

Try using diskpart to assign a drive letter to Disk #0, Partition #1.

·          Click Start Orb > type diskpart

·          Right-click diskpart in results above > click Run as administrator

·          Once diskpart loads type list volume, press enter

You should notice that you will see your partition that you use for your data, it should not show a drive letter assigned to it.

·          Type select volume 6 **** (replace 6 with the volume number assigned to the partition in question)

·          Type assign letter Z (replace Z with the letter that you want to assign to it)

When you look in Computer, you should be able to see your partition.

Hope this helps


Chris.H

Microsoft Answers Support Engineer

Visit our Microsoft Answers Feedback Forum and let us know what you think.

Was this answer helpful?

200+ people found this answer helpful.
0 comments No comments

156 additional answers

Sort by: Oldest
  1. Anonymous
    2010-08-13T05:42:00+00:00

    its seems that in order to fix this problem.... open divice manager locate the drive under disk drives, uninstall the drive, unplug it, plug it back in and it will reinstall the drivers and the drive should now work.

     

    Usnure as to why this has to be done on a plug and play device and why windows 7 couldnt istall the correct driver in the first place but it worked for me. goodluck

    This is definitely part of a good simplified solution for this problem, and I think I may have figured out part of the reason for it while solving my own issues.

    I had this problem with a 500G Adata remote hard drive on my computer after installing Windows 7 to a blanked internal drive. (Windows Boot Loader had been accidentally erased by GRUB when dual booting linux.)  When I plugged in the remote drive, it installed the driver, but failed to mount the drive, just like everyone else has mentioned.  (an unmounted drive will show up in devices etc. but not in My Computer.)  While messing with diskpart in an attempt to solve my problem I noticed AUTOMOUNT in the list of commands.  This command "enables and disables the automatic mounting of basic volumes."  On my system, automount was turned off.  After enabling it using the command, I found my remote hard drive in the device manager, and uninstalled the driver.  Unplugging and plugging the drive caused the computer to again install the driver, but this time it mounted it in My Computer as well.  Now my device was visible in said location, but for some reason my access was denied.  I resolved this by enabling sharing under the advanced sharing tab in the device properties.  Problem solved.  I can now use the drive and did not have to use disk management or format anything.

    To recap, my understanding is that on some instances of Windows 7, the automount function of the operating system is deactivated through some oversight or error.  This causes the system to not mount some removable storage devices when it discovers and installs them for the first time.  An unmounted drive will not be assigned a letter or volume and therefore may not be accessed by the user.  This problem is remedied by enabling automount using the command in diskpart, and then uninstalling and reinstalling the device.  I am not sure why my particular device was initially installed without giving me permission to access it, but I believe it to be a unique occurrence and an easily solved hang up compared to the device not mounting at all. 

    For the record, I have not managed to mount the smaller partition on my internal drive and I do not belive that much of the above will help with the mounting of multiple partitions of a hard drive.

    Was this answer helpful?

    0 comments No comments
  2. Anonymous
    2010-08-24T08:14:22+00:00

    ... While messing with diskpart in an attempt to solve my problem I noticed AUTOMOUNT in the list of commands.  This command "enables and disables the automatic mounting of basic volumes."  On my system, automount was turned off.  After enabling it using the command, I found my remote hard drive in the device manager, and uninstalled the driver.  Unplugging and plugging the drive caused the computer to again install the driver, but this time it mounted it in My Computer as well.  Now my device was visible in said location, but for some reason my access was denied.  I resolved this by enabling sharing under the advanced sharing tab in the device properties.  Problem solved.  I can now use the drive and did not have to use disk management or format anything.

    Yay! This worked for me using Windows 7! Here is the step by step version:

    1. From RUN, type diskpart and click OK
    2. At the DISKPART prompt, type automount
    3. From the Device Manager , find the device not being recognized. Mine was under Storage Devices, I think.
    4. Right click on the device and choose Properties
    5. Click on the Driver tab
    6. Click Uninstall
    7. Unplug the device
    8. Plug the device back in

    The driver was automatically installed, it's mounted to My Computer and I immediately got the AutoPlay window.

    Was this answer helpful?

    0 comments No comments
  3. Anonymous
    2010-09-01T02:43:11+00:00

    Yeah, uninstalling the driver worked for me, too. Worked like a charm!

    Was this answer helpful?

    0 comments No comments