Besoin d’aide pour une mise à niveau windows 11 sur un PC de bureau ancien
Bonjour à tous, j’utilise actuellement Windows 10 sur un PC de bureau âgé d’environ 7 ans et je me demande s’il est possible de passer à Windows 11 sans trop de complications. J’ai lu que certains matériels plus anciens peuvent poser problème, notamment au niveau du processeur ou du TPM, et je ne sais pas si une mise à niveau windows 11 est réaliste dans mon cas. Avant de me lancer, j’aimerais avoir vos retours d’expérience et vos conseils sur les méthodes possibles, les risques à connaître et les points à vérifier. Pensez-vous qu’une mise à niveau windows 11 soit recommandée pour un PC de cet âge, ou vaut-il mieux rester sur Windows 10 pour le moment ? Merci d’avance pour votre aide.
Bluetooth driver disappears after every restart/sleep on Windows 11
Dear Support Team, I am writing this complaint out of sheer frustration after enduring a critical Bluetooth driver issue on my Windows 11 laptop for an unreasonably long time. Every single time I restart my system or wake it up from sleep, the Bluetooth driver completely disappears from the system. It is not just disabled — it is gone. Bluetooth vanishes from Device Manager, settings, and system controls as if the hardware itself never existed. The only way to restore Bluetooth functionality is to reinstall the driver manually every time. This issue occurs: After every restart After waking the system from sleep Randomly during normal usage The frequency is so high that I have been forced to keep a Bluetooth driver installer shortcut permanently on my desktop — something that feels absolutely absurd for a modern operating system in 2025. Let me be very clear: This is not a user error This is not a one-off bug This is not acceptable behaviour for a premium Windows device I have tried: Reinstalling drivers multiple times Using official OEM drivers Updating Windows fully Disabling power management options Troubleshooting through Device Manager Running system diagnostics None of these provides a permanent fix. The core issue is painfully obvious: Windows 11 (or its driver/power management stack) is failing to reliably retain or initialise the Bluetooth driver across restarts and sleep cycles. This is a basic OS-level responsibility. As a long-time Windows user, I find it shocking that in a system where I spent a considerable amount, I am dealing with an issue that feels more appropriate for an unstable experimental build, not a consumer-ready operating system. To be completely honest, this experience has pushed me to the point where I am seriously considering abandoning Windows altogether and switching to macOS, despite having used Windows on my personal machines for years. The idea of paying that amount again just to escape such basic reliability problems is becoming more appealing than continuing to fight my own laptop daily. This is not just a “bug report” — this is a usability failure that affects: Work productivity Meetings Audio devices Input devices Everyday usability I expect: A clear acknowledgement of the issue A concrete explanation of why this happens A permanent fix, not temporary workarounds Or an official statement admitting the limitation I am documenting this issue publicly and will be sharing it across relevant forums and feedback channels unless a meaningful resolution is provided. Windows users should not have to reinstall core drivers every day to use basic hardware features. I look forward to a serious response. Sincerely, A very frustrated but still hopeful Windows user
Excessive ram usage in Windows 11
Hi there Since installing the Windows 11 1/2026 update, my PC has been using an excessive amount of ram. My Desktop has 32 Gigs of ram and while sitting idle, just looking at the desktop without having anything running and only some programs running in the background, the ram usage is about 25 gigs constant. Before the update the average usage while using my PC was around 15 to 20 gigs and that's while actively using it and having multiple programs running, including heavier things like CAD and stuff. Tried rolling back the update by booting into the recovery menu and uninstalling the update, but it didn't help. Any Ideas on how to fix it?
Installation Failure of KB5074109 on Windows 11 25H2 Multi-Session – Error 0x80073712
We are experiencing persistent issues installing the latest Windows update, KB5074109, on Windows 11 25H2 Multi-Session running in Azure. The installation fails on multiple machines with error code 0x80073712. We have tried the following troubleshooting steps, but still the same issue: sfc /scannow DISM.exe /Online /Cleanup-Image /RestoreHealth Windows Update Troubleshooter (Settings → System) Manual download and installation of the update Has anyone else run into this, or does anyone have ideas on how to fix it? Could the update itself be the problem?
Windows Subsystem for Linux doesn't work after the reinstallation of Windows 11 version 24H2.
I am not able to use Windows Subsystem for Linux after I reinstalled Windows 11 Home version 24H2 after resetting my Dell Inspiron 5410 laptop. The same occurred with my friend on a Windows 11 Pro laptop. Before the reset, the Windows Subsystem for Linux was working fine on both of our laptops. I tried following these steps to fix the issues. 1. I tried "Turn Windows features on or off," in which I enabled Windows Subsystem for Linux, which should make me use Ubuntu on my Windows PC after upgrading to version 2 using a kernel update. when I tried to update the WSL kernel By downloading and installing the latest WSL 2 kernel from Microsoft’s WSL Kernel Update. https://learn.microsoft.com/en-us/windows/wsl/install-manual Step 4 It says, "This update is applicable to machines with the Windows subsystem for Linux." and does not install updates WSL allows the following features: Ubuntu terminal environment in minutes with Windows Subsystem for Linux (WSL). Develop cross-platform applications, improve your data science or web development workflows, and manage IT infrastructure without leaving Windows. Key features: - Efficient command line utilities, including bash, ssh, git, apt, npm, pip, and many more - Manage Docker containers with improved performance and startup times - Leverage GPU acceleration for AI/ML workloads with NVIDIA CUDA - A consistent development-to-deployment workflow when using Ubuntu in the cloud But "Turn Windows features on or off" did not help. 2. Then, I tried installing WSL manually with the following codes: https://learn.microsoft.com/en-us/windows/wsl/install-manual Step 1 - Enable the Windows Subsystem for Linux Step 3 - Enable Virtual Machine feature PS C:\WINDOWS\system32> .exe /online /enable-feature /featurename:Microsoft-Windows-Subsystem-Linux /all /norestart >> Deployment Image Servicing and Management tool Version: 10.0.26100.1150 Image Version: 10.0.26100.2605 Enabling feature(s) [==========================100.0%==========================] The operation completed successfully. PS C:\WINDOWS\system32> .exe /online /enable-feature /featurename:VirtualMachinePlatform /all /norestart >> Deployment Image Servicing and Management tool Version: 10.0.26100.1150 Image Version: 10.0.26100.2605 Enabling feature(s) [==========================100.0%==========================] The operation completed successfully. Although it ran, it was not helpful even after 100 percent installation, but it did not help. 3. I tried following codes in PowerShell as Administrator: wsl.exe --install wsl --install wsl.exe --update PS C:\WINDOWS\system32> wsl.exe --install Class not registered Error code: Wsl/CallMsi/Install/REGDB_E_CLASSNOTREG PS C:\WINDOWS\system32> wsl --install Class not registered Error code: Wsl/CallMsi/Install/REGDB_E_CLASSNOTREG none of these codes helped. 4. When I tried running the command Bash in PowerShell as Administrator. C:\Windows\System32>bash Class not registered Error code: Bash/CallMsi/Install/REGDB_E_CLASSNOTREG It did not run. 5. I verified virtualization is enabled in BIOS. Restart your computer and access the BIOS/UEFI (usually by pressing F2, Del, or a similar key during boot). Look for settings like Intel Virtualization Technology (VT-x) or AMD-V and ensure they are enabled. Save changes and reboot into Windows. 6. Another error was given Error: 1168 Error code 1168 usually translates to "Element not found" in Windows. This error indicates that some required files, registry entries, or features are missing or improperly configured. In the context of WSL installation. 7. I even tried reinstalling Windows, which did not help. 8. I installed Windows 11 (multi-edition ISO for x64 devices). https://www.microsoft.com/en-us/software-download/windows11 But this also does not fix my issue. 9. Even the Windows customer support team was not able to help. I guess this is the issue with most of the system. Please help me fix it. and there may be a bug in Windows 11.Possible to bypass Windows 11 cpu check with rufus?
When I run the Windows 11 setup.exe from mounted ISO file, an error message shows: This processor isn't supported for this version of Windows. The CPU is an Intel Core 6700K. It seems this old PC doesn't meet the official CPU and TPM requirements. Could someone please confirm the exact steps to bypass Windows 11 cpu check with rufus? I want to make sure I select the correct settings to skip the compatibility checks during installation without causing any other issues. Any additional tips would be greatly appreciated.
Windows 11 Recovery Logic and BitLocker Default Issues Causing Boot and Reset Failure
I recently submitted critical feedback through the Windows Feedback Hub regarding a recovery failure scenario that blocked a system reset and was compounded by BitLocker being enabled by default without clear consent. After a normal shutdown, the system failed to boot. A reset attempt was blocked by Windows and required file deletion. At the same time, the system could not boot, making file deletion impossible. This forced a clean install in order to recover functionality. BitLocker was enabled by default, with the recovery key tied to a Microsoft account that was not actively managed. No documentation or guidance was provided to explain this circular recovery logic. I did eventually find a workaround, but a recovery process should never require undocumented steps or technical workarounds simply to regain access to one’s own machine. This represents a design failure, not user error. I submitted this issue as high severity under Install and Update, Backup and Restore, with the problem classified as Inability to use my PC. Feedback Hub link: https://aka.ms/AAzbsvg My key concerns are that boot and reset should not be blocked by opaque security defaults, BitLocker should be opt in and clearly explained during setup, recovery logic must be logically consistent and accessible, and a consumer operating system should not require undocumented workarounds to restore functionality. I also raised broader platform concerns including Windows 11 cost and value compared to macOS annual free operating system updates, ongoing install and uninstall friction caused by legacy registry behavior, and Apple’s predictable recovery process and system reliability. This is not bias. It is professional experience based on decades of use, certification, and paying customer history. I am sharing this here to increase visibility and open discussion, with the hope that engineers and other users can engage with the severity of this real-world failure mode.Secure Boot Certificate Updates via InTune Policy
We are currently having issues applying the settings required to install secure boot cert updates using the InTune policy method. A brief overview to quickly explain : We are a reasonably large company managing a mix of over 10,000 Windows and iOS devices. Our Windows devices come from the supplier with the Professional edition of Windows pre-installed, this is then changed via an Enterprise key as part of our Autopilot enrolment process and activated via our users subscription license. To all sense and purposes Windows looks and feels like the Enterprise edition, indeed if you check using winver, system settings and activation status for example then Windows tells us that it is the Enterprise edition. However, if you check the licensing using slmgr /dli it shows that the licensing has been reverted back to the OEM Professional edition as pre-installed by the supplier on purchase. This may have always been the case but until very recently has gone unnoticed. Whilst testing the rollout of an InTune policy to allow secure boot cert updates as detailed here : Microsoft Intune method of Secure Boot for Windows devices with IT-managed updates - Microsoft Support , this is failing because the policy is rejected by licensing error : MDM PolicyManager: Policy is rejected by licensing, Policy: (ConfigureMicrosoftUpdateManagedOptIn), Area: (SecureBoot), Result:(0x82B00006) Unknown Win32 Error code: 0x82b00006 InTune reporting directly on the policy shows this as error 65000 We are able to change the key by using slmgr and a combination of MAK\KMS\OEM but whatever keys are applied this always reverts to being the OEM Professional key after the device has been restarted. I have seen that there is a group policy method for setting the required settings for the secure boot cert updates to work, this however seems a very backward approach by Microsoft in an area where they are trying to promote a cloud-first policy. Indeed since we rolled out Windows 11, we as an organisation have been moving anything that we can to cloud in readiness for retirement of our on-prem estate. Microsoft's response to my recent support request was that this is expected behaviour, which to all sense and purposes is not what i would class as a solution. Has anyone else had the same issues when using the InTune policy method, and was a solution found or did you have to return to the dark ages and resort to group policy? There seem to be lots of posts online referring to access to specific registry keys being blocked going as far back as 2024, the suggested script to resolve these permissions and suggested KB articles have not resolved the issue.
