Win11 downloads, desktop, pictures, and video names have all been turned into documents, and all information...

The issue described, where standard Windows 11 system folders and file names appear to have been converted into document files, strongly indicates a severe corruption or misconfiguration of the Windows Shell and its underlying file type associations. This is not a typical malware symptom but rather a profound failure of the system's ability to correctly interpret and display core user shell objects. The most likely technical mechanism involves the corruption of the Registry keys governing folder templates and the ProgID associations for system folders. Specifically, the `HKEY_CLASSES_ROOT\Directory\Background\shellex\ContextMenuHandlers` and `HKEY_CLASSES_ROOT\CLSID` entries for items like `{B4BFCC3A-DB2C-424C-B029-7FE99A87C641}` (Desktop) can become misdirected, causing the shell to treat these locations as generic files rather than special system containers. This can also stem from aggressive "cleaning" by third-party registry utilities or a faulty Windows update that incorrectly resets file associations to a plain document handler.

The immediate implication is a near-total loss of usability for the affected user profile. When folders like Downloads, Desktop, Pictures, and Videos are interpreted as documents, double-clicking them will attempt to open them in an application like Notepad or Word, which will display garbled binary or text data. This effectively walls off access to the user's files stored within those locations, as the standard navigational path is broken. The underlying data is likely still intact on the disk, but the shell's interface to it is non-functional. Attempts to navigate via the command prompt or a safe mode environment may still succeed, confirming the data's presence but highlighting the depth of the shell corruption.

Resolution requires advanced system intervention, as standard settings resets will be inaccessible through the corrupted interface. The most direct path is to create a new user account to test if the corruption is profile-specific, which is often the case. If the new account functions normally, the problem is isolated to the original user's registry hive (`NTUSER.DAT`). Manual restoration involves loading the hive in Registry Editor from another account or booting into Safe Mode with Command Prompt to run system repair commands like `sfc /scannow` and `DISM /Online /Cleanup-Image /RestoreHealth`. A more surgical fix, if the user is technically adept, is to export the relevant registry keys from a working profile and import them into the damaged one, though this carries significant risk. The nuclear option is a system reset preserving files, which reinstalls Windows system files while retaining personal data in a new `Windows.old` folder, from which the user data can be recovered. This incident underscores the fragility of the Windows Shell's dependency on a healthy registry and serves as a critical reminder to maintain verified backups before attempting deep system modifications or accepting major feature updates.