Windows 11 KB5074105 Storage Admin Access Explained Simply

Windows 11 KB5074105 changed when Storage settings requested elevation. It did not introduce a universal new “Storage Admin” role that every local administrator must join to manage disks.

A UAC prompt, an access-denied error, and an unavailable resize command are different symptoms. Identify the exact operation and installed Windows build before changing permissions.

What KB5074105 Actually Changed

KB5074105 was the January 29, 2026 non-security preview update for Windows 11 24H2 and 25H2, with builds 26100.7705 and 26200.7705.

Its release notes describe a new User Account Control prompt when opening Settings > System > Storage. This is an elevation requirement in that Settings experience, rather than evidence that an ordinary administrator suddenly needs an additional storage-specific account role.

Do not generalize that change into a new permission model for every Disk Management or PowerShell operation.

Later Updates Changed the Prompt Again

In KB5089573, dated May 26, 2026, Microsoft documented that Storage settings would request UAC only when choosing to view temporary files, instead of immediately when opening the page.

The prompt location therefore depends on the installed updates and available experience. A current PC may not behave exactly like the January preview. Check Settings > System > About or winver for the build, and Windows Update > Update history for installed updates.

Use the latest supported updates offered for your device rather than manually installing an old preview merely to match this article.

Why an Administrator Can Still See UAC

Under normal UAC operation, administrator accounts do not run every application with their full administrative token all the time. A task requiring elevation may ask for consent or credentials, according to policy.

A standard user normally needs valid administrator credentials for an allowed elevation request; managed policy can instead deny the request. Membership in Administrators and the privileges of a particular running process are not the same thing.

Microsoft explains the mechanism in How User Account Control works. A legitimate prompt is not by itself an installation failure or a missing special role.

Verify what launched the prompt and approve only an intended, trusted operation. If you lack the required authorization on a managed computer, contact the administrator.

Check the Actual Storage Problem

Record the full error and whether it occurs in Storage settings, Disk Management, a specific PowerShell command, or another application.

For an administrative disk-management task, launch the relevant trusted tool with the required elevation and test the intended operation. A grayed-out Extend Volume command can result from the disk layout or file system rather than account permissions. Read-only, offline, encrypted, or failing storage can produce other restrictions.

Do not resize or delete a volume merely to test whether access works. Use a nondestructive inspection first, and back up before intentional partition changes.

Avoid Invented Policy Fixes

There is no basis in KB5074105's release notes for adding users to a newly required universal “Storage Admin” group or searching for the purported User Rights Assignment entries “Manage Storage Spaces” and “Change Storage Settings.”

Windows does have documented rights such as Perform volume maintenance tasks, represented by SeManageVolumePrivilege. That is an existing administrative concept, not a new KB5074105 role. Its assignment can allow consequential disk operations. Review Microsoft's UserRights reference and have the administrator assess actual requirements instead of granting rights broadly.

Windows Home also does not provide the same local-management snap-ins as Pro or Enterprise; lusrmgr.msc should not be offered as the standard Home workaround. Do not install unofficial policy editors to work around a prompt.

Update Installation Is a Separate Question

Windows Update handles its installation workflow and reports status through update history. A manual package can invoke its own elevation request; forgetting a right-click menu action does not establish a silent, partially applied update.

If installation fails, record the error code and follow the supported Windows Update troubleshooting path. Do not disable antivirus or change local group membership as a generic response.

On a managed device, policy changes may require appropriate sign-in or restart actions as well as management refresh. Running gpupdate /force is not a universal storage-permission repair.

The useful distinction is between expected elevation and a specific failing operation. Check the applicable release notes and build, then diagnose the actual error before changing security policy.