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?Feature Request: Enhanced system restore UI like virtualization software
Hi Microsoft dev community, I insist implementingfunctionality to take snapshot/restore actual hard drive system restore restores pc back in time in case of issues but not as user friendly as any virtualization software like vmware Just as virtualization software there can be a more advanced version of system restore application where there will be UI for: 1. taking snapshot of current state 2. option to list snapshots 3. restore any snapshot back in time Maybe based on Hyper-V, Maybe this feature already there but I have not found it originally posted here: https://superuser.com/q/1855140/86839Quality Updates Learn More sites are not found error
I am getting an error every time I select Learn More in Update History " Quality Updates". The websites are not found. Just wondering if this is a known issue for windows insider build that I am also running now. I have attached screenshots to explain more about the issue. All the KB Articles cannot be found.Windows 11 insider Dev build 25309 allows for uninstallation of VBSCRIPT
You can now uninstall VBSCRIPT You can either use Windows settings -> Apps to uninstall it or use the PowerShell script below: Get-WindowsCapability -Online | Where-Object { $_.Name -like '*VBSCRIPT*' } | remove-WindowsCapability -Online
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
