STATUS_NO_QUOTAS_FOR_ACCOUNT (0X0000010D) Fix
This Windows error means your account lacks quota limits, often triggered by a corrupted user profile or Group Policy misconfiguration. Here's how to fix it fast.
1. Corrupted User Profile
This is the culprit about 80% of the time. You'll see this error when logging into Windows 10 build 22H2 or Windows Server 2022 after a forced reboot or a disk cleanup tool went rogue. The error text—No system quota limits are specifically set for this account—is Windows throwing its hands up because your profile's quota settings are missing or corrupted.
Fix: Delete and recreate the user profile
- Press Win + R, type
sysdm.cpl, hit Enter. Go to the Advanced tab, under User Profiles, click Settings. - Find the profile showing the error (look for the account name). Select it, click Delete. Yes, this nukes the local profile — make sure you've backed up anything in Desktop, Documents, etc.
- Log off and log back in. Windows recreates a fresh profile. The error should be gone.
Pro tip: If you're on a domain, also check C:\Users\Default\NTUSER.DAT isn't read-only — seen that trip up plenty of admins during OS upgrades.
2. Group Policy Blocks Quota Settings
Sometimes the error isn't a profile issue, it's the Group Policy Object (GPO) preventing quota limits from being applied. I've seen this mostly in corporate environments where IT locked down disk quotas. The error pops up every time a user tries to access My Computer > Properties.
Fix: Enable quota setting via Local Group Policy
- Run
gpedit.mscas Admin. Navigate to Computer Configuration > Administrative Templates > System > Disk Quotas. - Double-click Enable disk quotas. Set it to Enabled.
- Then set Apply policy to removable media to Disabled (unless you need quotas on USB drives, which you probably don't).
- Run
gpupdate /forcein an admin command prompt and reboot.
If the policy was already enabled, switch it to Not Configured, apply, then back to Enabled. That refreshes the policy without waiting for the next refresh cycle.
3. Registry Corruption in Quota Keys
This one's rarer but nasty. The registry key HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Quota gets clobbered by third-party disk utilities (looking at you, older versions of CCleaner). You'll see the error during Windows Update or when running chkdsk.
Fix: Restore default quota registry values
reg add "HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Quota" /v Start /t REG_DWORD /d 1 /f reg add "HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Quota" /v Type /t REG_DWORD /d 1 /f reg add "HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Quota" /v DisplayName /t REG_SZ /d "Disk Quota Driver" /fRun those three commands in an admin command prompt. Reboot. That forces the Disk Quota driver to start on boot. If the Quota key doesn't exist at all, create it manually: right-click Services, choose New > Key, name it Quota, then add the values above.
Quick-Reference Summary Table
| Cause | Symptom | Fix | Difficulty |
|---|---|---|---|
| Corrupted user profile | Error on login or profile load | Delete profile via System Properties | Intermediate |
| Group Policy blocks quotas | Error when accessing disk properties | Enable disk quotas in gpedit.msc | Intermediate |
| Registry corruption | Error during updates or chkdsk | Restore Quota service registry values | Advanced |
Try the user profile fix first — it's the fastest and most likely to work. The Group Policy fix is your second stop. The registry fix is for the stubborn cases where nothing else helps.
Was this solution helpful?