[BUG]Desktop Icon Order and File Explorer Window Size Not Saved
After updating to Build 26200.5661, I found two major issues: 1. The desktop icon order is not retained after reboot or shutdown. Every time the system restarts, icons are randomly rearranged. 2. The File Explorer window size is not remembered. It always resets to the default size after closing and reopening. These issues did not occur in the previous build. Expected behavior: - Desktop icons should retain their order and position. - Explorer windows should remember their last size and position
Recall fails to start and always asks me to log in using Windows Hello
"My Windows version is 26120.3073. Recall had always worked properly on my computer, but today after restarting my computer, it no longer works and remains in a paused state, prompting me to log in using Windows Hello to resume. I logged in using Windows Hello, but Recall did not resume and still prompts me to log in using Windows Hello to resume. I have tried various methods, including opening Recall, re-logging into Windows, putting the computer to sleep and waking it up, restarting the computer, disabling and enabling the Recall function, but none of these methods solved the issue. It consistently prompts me to log in using Windows Hello to resume. I also checked TPM and Windows Hello, and both are working properly.
Facing Issues with Insider Preview (27808.1000)
Hello, I’m facing an issue where my graphics application (Autodesk Fusion 360) only works when I disable my NVIDIA graphics driver. However, as soon as I enable the driver, the application stops working. System Details: GPU Model: NVIDIA 1650 Operating System: Windows 11 Insider Preview 27808.1000 (rs_prerelease) Driver Version: NVIDIA Driver Version 572.70 Application Affected: Autodesk Fusion 360, OpenSCAD Troubleshooting Steps I’ve Tried: Reinstalled the NVIDIA Driver (Used a clean installation from the official NVIDIA website). Tried Rolling Back the Driver (If a newer update caused the issue). Checked NVIDIA Control Panel Settings (Set preferred GPU to NVIDIA, power management to maximum performance). Verified Windows Updates (Ensured my OS is up to date). Checked for Application-Specific Compatibility Issues.Windows on exFAT has some bugs
As shown in the screenshot attachment, when using the exFAT file system as the system volume to run the latest version of Windows 11 Build 27686, the following bugs exist: 1. When the Shim DataBase file exists, the system UWP such as the start menu and settings cannot be opened. If you delete the file named "RandomGUID.sysmain.sdb" in the "C:\Windows\apppatch\MergeSdbFilesSource" directory, or delete the registry "HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\AppCompatFlags\SdbUpdates" item, the problem can be solved. This bug has existed since Win11 v22H2 two years ago and has not been fixed yet. 2. When the Smart App Control function is in the evaluation or enabled state, the operating system will run very slowly. If you set it to off in app & browser control in Windows Security, or directly change the "VerifiedAndReputablePolicyState" key value in the registry "HKEY_LOCAL_MACHINE\SYSTEM\ControlSet001\Control\CI\Policy" to "0" to turn it off, the problem can be solved. This bug has existed since Win11 v22H2 two years ago and has not been fixed yet. 3. Check Disk Utility will throw an error when checking exFAT volumes with a total number of clusters between 2^30 and 2^32 (that is, the FAT table size is between 4GB and 16GB), but in fact the volume is completely normal and not damaged. In addition, according to the exFAT file system specification, a single exFAT volume can have a maximum of 4294967295 allocation units, which means that the maximum partition capacity supported by formatting with 4KB clusters is 4096Byte×2^32Byte=16TB. However, when trying to load a volume of this size, it takes a long time to complete the operation, which may be another bug. 4. The change partition size function in the disks & volumes in the new system storage settings will cause file system corruption and loss of all data when operating on exFAT volumes. If the volume is a system partition, it will immediately trigger BSOD and cause the OS to completely crash and fail to start. This is a very dangerous bug. 5. When the system Blue Screen of Death occurs, the DUMP file cannot be generated normally in the exFAT volume. This seems to be a bug in exfat.sys. 6. When the system volume is exFAT, the hiberfil.sys file cannot be created normally, resulting in the inability to use the hybrid boot function. The 0xc0000010 error will also be prompted through command line operations. This seems to be a bug in exfat.sys. 7. Every time try to run a user UWP app such as Microsoft Store, the AppX Deployment Service will repeatedly stop abnormally, causing the UWP program to crash immediately. This seems to be a bug in AppXDeploymentServer.dll. Please fix these bugs, thanks! In addition, it usually takes a long time to boot Windows in the exFAT volume. Can you optimize the boot speed of exFAT system volumes in OS Loader?
Changing monitor input causes windows to maximize over taskbar.
I have this issue when changing inputs on my monitors. When going from my work computer to my pc, my pc will adjust all my windows to maximize over the taskbar. When using this browser for example, it appears as if my taskbar is hidden. However, I do not have the taskbar on autohide. If I minimize the window my task bar appears as usual, as it should. Any window (browsers, spotify, discord, etc...) that is maximized covers the taskbar. The only work around I have found for this is by adjusting the display resolution, and then reverting. Something about the temp resolution change causes the functionality to return to normal. I have ran all updates and cannot find anyone that has reported similar issues.
Roll back to previous Insider Build
Hello I am Currently on Windows 11 Insider Preview 10.0.26052.1100 (ge_release) Ive had some issues with the Taskbar Prewiev and with Multitasking. I wanted to Roll back to Windows 11 Insider Preview 23619.1000 (ni_prerelease) which was working flawlessly. Any guide on how to perform that?
Windows 11: Double taskbar profile icon when opening Chrome profile
I found a bug in Windows 11 when I opened a chrome profile, it shows up two profile icons instead of just one (see the screenshot). In Windows 10, it used to open with the bottom-right icon, but I think Windows 11 added a new place for the icon in the upper-right, but overlapping it with the old icon place instead of replacing it. Device and OS Spesification: Edition: Windows 11 Enterprise Version: 21H1 Build: 22000.100 Is it just for me or everyone else have the same problem? If so, I hope this bug can be fixed in the next update. Thank you.
Windows 10 22H2 can be rendered unbootable if ''Windows Fax and Scan'' is removed
There is a serious bug in the 32-bit kernel releases (x86) of Windows 10 22H2 (though older versions, such as 21H2 or 21H1 may also be affected; I have not tested). I was doing some test-installs of the latest 22H2 release, using install-media built from the Media Creation Tool. (The version that this tool creates is currently Build 19045.2006). To reproduce this bug, do the following: 1 Install the x86 version of Windows 10 Version 22H2 onto a PC, or inside a VM (e.g. Home or Pro) 2 After the Desktop appears, go to Start > Settings > Apps > Optional Features 3 Click "Windows Fax & Scan" in the list, then the "Uninstall" button 4 After the uninstall is finished, and "Reboot required" appears, restart the PC or VM session 5 During the next boot-up, it will first go to this screen briefly: "Updating your system 0%" But will then go to a blue-screen with this error: Stop code: KMODE_EXCEPTION_NOT_HANDLED What failed: NTFS.SYS 6 After a reboot, the blue-screen will appear again, then after the next reboot Windows will go to the "Preparing Automatic Repair" screen 7 The only way to repair the Windows install is to use a System Restore point, should one exist I have been able to replicate this issue on ALL x86 kernel installs of Windows 10 22H2 I have tested, but the 64-bit (x64, AMD64) kernel versions are unaffected. I have no ARM devices to test. Needless to say, this should be treated as critical as this is easily reproduceable, and uses only built-in options supplied with Windows, but leaves systems completely unbootable afterwards. Thanks
