"Partition is not accessible. Access is denied."


Recommended Posts

post-151617-0-44558000-1355767118.jpg

OK, I'll try to be as detailed as I can with this. Originally, I was trying to size down my system partition in order to clone it onto my SSD, by clearing as much space as I could, then creating a second partition and moving non-system files over, resizing when needed (only had to be done three times). The first resize went off without a hitch, but the second one ended up completely botching my Windows installation to the point where it was unusable and unrecoverable, so I had to resort to a fresh install of Windows 8 straight onto the SSD (which I know is the recommended method; I just didn't want to resort to reinstalling every single program of mine again). Now, since then, everything's been fine, except for the former system partition on the HDD. It refuses to let me browse it (as seen in the screenshot above). Weirdly however, I can see the folders if I explore it in EASEUS Partition Master. Now, I have Google searched to try and find a solution; the common one that pops up is to grant all privileges to my account, which has already been done. Another suggestion was to convert it to a dynamic volume, but that hasn't worked either (and annoyingly, I can't convert it back to a basic volume now). I've also done a S.M.A.R.T. check, ran CHKDSK, ran SFC /scannow, all they all come back with no issues.

Does anyone know any other potential solutions for regaining access to the drive, without losing any of the files? A fair bit of my personal stuff is on there (documents, pictures), as well as a lot of Steam game files; I really don't want to have to resort to redownloading several hundred GBs again.

Obviously, I have been an idiot for not having a backup; I'm planning on rectifying that by buying an external HDD soon; preferably a 2TB one, so I can back up both HDDs.

I have had this in the past and although I can't remember the exact method I used, I do remember what kind of settings I had to change.

Aswell as giving myself the necessary privileges, I needed to take "ownership" of the drive. Right click, Properties, Security, Advanced, Owner then chose my user account. I'm pretty sure this then let me access all the files on the drive after Windows went mental one afternoon and locked me out. Could be worth a try?

I have had this in the past and although I can't remember the exact method I used, I do remember what kind of settings I had to change.

Aswell as giving myself the necessary privileges, I needed to take "ownership" of the drive. Right click, Properties, Security, Advanced, Owner then chose my user account. I'm pretty sure this then let me access all the files on the drive after Windows went mental one afternoon and locked me out. Could be worth a try?

Thanks for the reply. I'll just give that a go now...

post-151617-0-87843200-1355783540.jpg

...nope, no luck, I'm afraid. According to the window, I have already taken ownership of the drive.

You installed a NEW OS?? The SID changed, whatever permissions you set on that drive are no longer valid because you have a new OS. Take ownership and there you go. Access to drive, unless you had used something like EFS and you don't have the keys now that you installed a new os, etc. Then you might be F_cked!

edit: just because you have ownership, does not mean you have access - just give your account the permissions you want, owner can always set permissions.

You installed a NEW OS?? The SID changed, whatever permissions you set on that drive are no longer valid because you have a new OS. Take ownership and there you go. Access to drive, unless you had used something like EFS and you don't have the keys now that you installed a new os, etc. Then you might be F_cked!

edit: just because you have ownership, does not mean you have access - just give your account the permissions you want, owner can always set permissions.

According to this window...

post-151617-0-03789300-1355783905.jpg

...my account has full control. The special permissions field is blanked out when I try to allow that, however. And when I try to change anything at all there, I'm greeted with this...

post-151617-0-18658800-1355783974.jpg

Oh, and I did try to retake control. I used this method to take ownership, and I'm still being denied access.

One more screenshot for now, just to show something on my PC can at least access the partition...

post-151617-0-65648700-1355784180.jpg

I got the failed to enumerate the other day while cleaning up the Windows.old on some Server 2012 upgrades. I had to drill down a few folders, take ownership, then delete then go back up a few directories, take ownership then could delete it all - it was like it completely ignored permissions (and even the ones I was trying to assign/take owner of) until the trash was cleaned out.

According to that windows the Administrators group has permission, not your account.

Your account may be a member of admins - but until you elevate it would not be running with an admin token.. Give YOUR ACCOUNT permissions, or the users group, or the everyone group.

BudMan, you're a (virtual) lifesaver. :woot: I just just tried to give permissions to "Everyone", and my username, and I get the same "Failed to enumerate..." error as posted above, but the permissions stay in the window, and it's finally accessible again! :) Only thing that came up when I accessed the properties again was a message telling me the Recycle Bin on that drive was corrupted, so I just emptied it (There was obviously nothing of any use in there).

Sorry for misreading your original post. :p

"Failed to enumerate..." objects in the container - I would have to assume it has ACLs set to accounts that are not longer available for the reason for those errors somewhere down the line.

You could prob remove the error by completely writing the permissions down the tree with your new accounts,

  • 1 year later...
This topic is now closed to further replies.
  • Posts

    • How many other companies will follow Ford's lead? Or, have they already gotten lazy and become enslaved to AI--and now can't figure out how to get out of that mess.
    • Why would any self-respecting intelligent person follow any recommendation by Donald's GOP administration? With almost two years of fabrications, deceit, and blatantly illegal behavior, why believe them now? They had best be gone after the November 2026 election, so we'll wait and see.
    • AltSendme 0.4.1 by Razvan Serea AltSendme is a minimal, cross-platform application designed for fast, secure, and private peer-to-peer file transfers. It allows users to send files or entire directories directly between devices without relying on cloud servers, accounts, or any personal information. Everything is encrypted end-to-end using modern protocols like QUIC and TLS 1.3, ensuring both strong security and low-latency performance. Transfers are verified with BLAKE3 for data integrity, and interrupted downloads automatically resume, making the experience reliable even on unstable connections. You can transfer anything—images, videos, documents, and more. Integrity checks are performed on both ends, so your files are automatically verified for correctness during both sending and receiving. AltSendme works seamlessly across local networks or long-distance links, capable of saturating multi-gigabit connections for extremely fast delivery. With built-in NAT traversal and encrypted relay fallback, it connects devices almost anywhere. The app integrates with the Sendme CLI and will soon support mobile and web platforms. Fully free and open-source, AltSendme offers a lightweight, privacy-first alternative to traditional cloud-based services, removing size limits, upload costs, and unnecessary data exposure. AltSendme 0.4.1 changelog: Release Highlights Self-hosted relays: Run your own iroh relay so transfers don't rely on public infrastructure. Includes a full deployment template in deploy/relay/ with Docker Compose for a VPS and configuration examples for production use. Fly.io support: One-click deploy template for Fly.io, including a quick-start config (fly.dev.toml) for testing without a custom domain, plus production setup with Let's Encrypt and your own hostname. Relay settings UI: New Settings → Network panel to choose how AltSendme connects: automatic public relays, custom self-hosted URLs (with optional auth token), or disabled. Test connections, verify latency, and see live relay status in the footer. Disable relays: Turn off relay servers entirely when you only need same-network transfers (e.g. LAN). Direct connections only. No relay hop required when devices can reach each other. Android graduates from beta: Android is now part of the regular release cycle alongside desktop. APKs ship with each version (universal, arm64, and armv7). Other improvements Private relay access control via shared auth token Relay fallback notifications when a custom relay is unreachable Broadcast mode toggle in sharing settings Android release build fixes (split-per-ABI APKs, universal APK preservation) UI polish: mobile safe-area insets, dropzone layout, transfer progress animation Bug fixes for minification-related serialization issues and system tray icon loading What's Changed feat(relay): add relay status functionality and settings UI (a120cdf) feat(relay): implement custom relay server configuration and verification (51276c7) feat(relay): add configuration for private relay access and enhance observability features (48fbabf) feat(relay): enhance relay URL validation, display connection status (d4fffa0) feat(relay): add RelayChangeGuard component and enhance relay-related translations (16ba514) feat(broadcast): add toggle setting for broadcast mode in sharing UI (ca6d977) fix(relay): correct QUIC discovery port, pin image, templatize fly.dev (52a2ba5) fix: More broken serialization due to minification (67491a9) fix(android): preserve true universal APK across per-ABI builds (e9f256f) fix(ui): conditional safe-area insets padding on mobile (1182f0e) refactor(transfer): CircularRing component animation fix (944572b) chore(android): drop x86 and x86_64 release APKs, keep universal+arm64+armv7 (34ada0b) Download: AltSendme 0.4.1 | ARM64 | ~9.0 MB (Open Source) Download: AltSendme for MacOS | Android Links: AltSendme Home Page | GitHub | Screenshot Get alerted to all of our Software updates on Twitter at @NeowinSoftware
    • You are mostly right about the ephemeral nature of it. As I mention in the article, if you dont add a second device or take a backup of your account before uninstalling it, then yes you will lose access to your account. That said, in terms of actual user experience when you sync multiple devices your message history carries across and there's also a Saved Messages chat like there is on Telegram to send messages and attachments between your installs. But yh, what you point out are correct and its not trying to emulate Messenger or Telegram.
    • OK so SearXNG is a meta search engine that you can install locally or use via a public instance. It scrapes other search engines which you choose and then sorts the results. Not as complicated as multiple relays
  • Recent Achievements

    • Week One Done
      flexorcist earned a badge
      Week One Done
    • One Month Later
      Woland13 earned a badge
      One Month Later
    • Week One Done
      Woland13 earned a badge
      Week One Done
    • One Year In
      bernmeister earned a badge
      One Year In
    • Week One Done
      Scoobystu earned a badge
      Week One Done
  • Popular Contributors

    1. 1
      +primortal
      492
    2. 2
      +Edouard
      224
    3. 3
      PsYcHoKiLLa
      150
    4. 4
      Steven P.
      75
    5. 5
      FloatingFatMan
      71
  • Tell a friend

    Love Neowin? Tell a friend!