Two separate issues are described here:
- USB pen drive is write-protected/locked
- The device is still receiving Windows Insider builds
For the pen drive write problem, if the PC is in a domain environment, the most common cause is a domain Group Policy that enforces USB write protection. Local registry or local policy changes can revert after restart.
Use this check:
- Open Command Prompt.
- Run:
gpresult /h gp-report.html - Review the report for policies under: Computer Configuration > Administrative Templates > System > Removable Storage Access
- Check whether Removable Disks: Deny write access is enabled.
- If it is enabled, set it to Not configured or Disabled. If the setting is controlled by the domain, the domain administrator must change it.
- Apply policy changes:
gpupdate /force - Test write access to the USB drive again.
Also check whether the USB drive itself has a physical write-protect switch.
For the Insider builds still appearing after reinstall, a reset or reinstall does not always remove the device from Insider flighting. To stop receiving Insider Preview builds on the device:
- Go to Settings > Windows Update > Windows Insider Program > Stop Insider Preview Builds.
- If the device is on Beta, Experimental, or Release Preview, turn on the option to stop getting preview builds. This returns the device to a retail build.
- If the device is on Experimental (Future Platforms), complete a clean installation of Windows 11.
Important: if the device receives Insider Preview builds through work or organization management, it will continue receiving them until the organization leaves the program or changes the settings.
If updates are still arriving, also verify:
- Settings > Windows Update > Windows Insider Program: confirm the channel and enrollment state.
- Settings > Windows Update > Check for updates.
- Whether the current build is already the latest build for that channel.
If Windows Update itself is behaving incorrectly, advanced repair steps exist, but they are higher risk and require administrator permissions. One supported path is resetting the Windows Update cache by renaming the SoftwareDistribution and Catroot2 folders from an elevated Command Prompt.