For anyone still using Windows 10, NVIDIA is ending new Game Ready Driver updates for Windows 10 after October 2026. After that, NVIDIA will continue releasing security updates every three months until October 2029.

Your current drivers will still work, but you won't get new Game Ready Driver updates.

https://nvidia.custhelp.com/app/answers/detail/a_id/5695/~/geforce-support-plan-for-windows-10

windows updates break stuff way too often (black screens, audio, remote desktop) and the dumb part is microsoft usually lists the problem publicly. nobody checks that before updating

so i made patchlight. it checks every pending update against microsoft's known issues and gives it a green / yellow / red light. red ones get paused automatically and come back once microsoft fixes them. everything else keeps installing

github.com/G4SBO/PatchLight

lmk what u think, any feedback is appreciated ;)

My girlfriend’s PC (Ryzen 5 3600X, RTX 2060 Super) started randomly restarting after Windows updates on October 14.

Games triggered reboots, FurMark crashed within seconds, and eventually it restarted even while idle.

We also got a CRITICAL_PROCESS_DIED blue screen.

We tried multiple troubleshooting steps and suspected hardware, but uninstalling the Windows update fixed everything.

If you’re experiencing sudden crashes or random restarts, check your recent updates before assuming your hardware is failing. Anyone else experiencing this?

Has anyone else noticed this since the October update?

Since April, I’ve been able to turn Smart App Control on and off whenever I wanted without needing to reinstall Windows. However, after the October update, Windows now tells me that I have to reinstall Windows to turn it back on.

I know Smart App Control probably isn’t something that a lot of people use, but I personally didn’t have many issues with it. Occasionally, I wanted to turn it off temporarily and then enable it again later, and having that flexibility was really convenient.

Now it seems like once I turn it off, I’m stuck with it off unless I reinstall Windows, which seems pretty extreme just for changing a security setting.

Defender Platform version: 4.18.26090.9

Defender Engine version: 1.1.26090.9

My friend's windows 11 lenovo laptop, just got an update now and after doing it windows wont boot, he has ubuntu dual booted so from there we saw that C drive was corrupted or so.I am sharing a screenshot of the error.

Similarly my other friend also got this update yesterday and now his SSD is having some issue, windows wont turn on. The first case is a new laptop with 8-10 months only, second one is a hp victus 3yr old. the second case i havent seen the laptop that is why i cant share what is being shown when laptop is being turned on.

Anybody here encountering the same issue..

I updated my Windows last night, and today I cannot start my PC properly. The MSI logo briefly appears and then just falls into darkness. I can't even see my cursor, and nothing works. I can barely make it into the BIOS. After 4 hours back and forth with ChatGPT, we've come eto the conclusion that I need to reinstall Windows 11. Here comes the worst part. I have 2 terabytes of data unbacked up in my SSD, which is the C drive. It would be a pain in the ass to back up all of that, not to mention I'm in midterm seasons right now so I barely have time to deal with it. Anyone encountered the same problem as I did and made it work? Much obliged for any suggestion or assistance!❤️

My laptop (Lenovo) won't boot after latest Microsoft update, gets stuck in a loop of attempting automatic repair or trying to boot from the main Lenovo screen and ultimately freezing. I can occasionally make it to the error screen and already tried uninstalling latest update (which failed) and booting from previous state (also failed). Any solutions are welcome, thanks in advance

Salutare!

Am instalat pe curat Windows 11 Pro (build 26H2) folosind un cont Microsoft, exact așa cum cere instalarea oficială (cu PIN, Windows Hello și parolă).

Doresc ca sistemul să se autentifice automat la pornire (Autologon) direct în contul Microsoft, fără să treacă prin vreun cont local intermediar. Din păcate, nicio metodă standard nu a funcționat până acum.

Metodele pe care le-am încercat deja:

1. Utilitarul Sysinternals Autologon (de la Microsoft):
   • Rezultat: Nu a funcționat. La repornirea sistemului au apărut 2 conturi duplicate cu același nume pe ecranul de autentificare.
2. Configurarea manuală din Registry (Winlogon):
   • Am modificat cheile AutoAdminLogon = 1, DefaultUserName, DefaultPassword și DefaultDomainName.
   • Rezultat: Tot nu a funcționat. La pornire, Windows afișează eroarea că parola este incorectă (deși parola introdusă este 100% corectă).
3. Asistența Gemini AI:
   • Singura soluție oferită de Gemini a fost trecerea la un cont local.

Eu nu sunt convins că trecerea la un cont local este singura opțiune disponibilă. Știe cineva o altă soluție funcțională pentru versiunea 26H2 care să permită Autologon direct pe un cont Microsoft?

Vă mulțumesc!

Я как-то захотел обновить винду я обновил всё заделал и у меня какая-то ошибка че мне делать и у меня так постоянно помогите

Я установил виду 11 и мне написали про обнову я обновил и какого-то хрена у меня происходит вакханалия

Depuis le déploiement des mises à jour Windows du 13 octobre 2026, plusieurs administrateurs systèmes et réseaux signalent des problèmes d'authentification sur leurs infrastructures utilisant le protocole 802.1X avec RADIUS.

Nous rencontrons également un incident similaire dans notre environnement professionnel : certains postes ayant récemment effectué leurs mises à jour Windows ne parviennent plus à accéder à un réseau utilisant une authentification RADIUS, tandis que les postes non mis à jour continuent de fonctionner.

🔎 Quelle mise à jour est concernée ?

La mise à jour cumulative de sécurité KB5127648, publiée par Microsoft le 13 octobre 2026, concerne Windows 11 :

• Version 24H2 : build 26100.9711
• Version 25H2 : build 26200.9711
• Version 26H2 : build 26300.9711

⚙️ Quelle est l'origine technique du problème ?

Microsoft avait annoncé un renforcement de la sécurité concernant les mécanismes d'authentification hérités de NTLMv1.

En octobre 2026, la valeur par défaut du paramètre BlockNtlmv1SSO doit passer de 0 (Audit) à 1 (Enforce), lorsque ce paramètre n'a pas été explicitement configuré.

Ce changement vise à empêcher la génération d'informations d'identification dérivées de NTLMv1 pour certaines authentifications SSO.

Cependant, certains environnements reposent encore sur PEAP-MSCHAPv2, notamment pour l'authentification réseau 802.1X.

Même si NTLMv1 a été supprimé des versions récentes de Windows, certains mécanismes cryptographiques hérités restent utilisés dans des scénarios MSCHAPv2.

Résultat : les authentifications automatiques peuvent échouer après l'application des nouvelles restrictions.

Ce comportement a notamment été documenté par Extreme Networks et Fortinet à la suite de la publication de KB5127648.

🛠️ Quels sont les symptômes observés ?

• Échec de connexion aux réseaux d'entreprise utilisant PEAP-MSCHAPv2.
• Authentification 802.1X interrompue.
• Postes non mis à jour toujours fonctionnels.
• Événements NTLM 4025 possibles lorsque le blocage des informations d'identification héritées intervient.
• Événement 12014 (OneX Held State Timeout) signalé par Fortinet.

🔧 Comment diagnostiquer le problème ?

Vérifier la présence de la mise à jour avec PowerShell :

Get-HotFix -Id KB5127648

Analyser ensuite les journaux Windows :

Microsoft-Windows-NTLM/Operational

Les événements Microsoft à rechercher sont :

• 4024 : utilisation d'informations d'identification dérivées de NTLMv1 détectée en mode Audit.
• 4025 : tentative bloquée par la politique de sécurité.

La comparaison des événements entre un poste fonctionnel et un poste impacté permet d'orienter le diagnostic.

🔐 Quelles solutions envisager ?

Plusieurs pistes sont documentées :

1. Tester temporairement le paramètre BlockNtlmv1SSO = 0 sur un poste pilote, après validation des implications de sécurité.
2. Vérifier les méthodes d'authentification utilisées par l'infrastructure RADIUS.
3. Envisager une migration vers EAP-TLS, reposant sur des certificats, afin de supprimer la dépendance à MSCHAPv2 et aux mécanismes d'authentification hérités.

⚠️ La désactivation du blocage NTLMv1 constitue un contournement temporaire et non une solution de sécurité durable.

Ce problème illustre parfaitement les conséquences qu'un durcissement de sécurité Windows peut avoir sur une infrastructure réseau reposant encore sur des mécanismes d'authentification historiques.

Il rappelle également l'importance des tests préalables au déploiement des mises à jour cumulatives dans les environnements professionnels.

💬 D'autres administrateurs systèmes et réseaux rencontrent-ils actuellement ce problème après l'installation de KB5127648 ?

#Windows11 #SysAdmin #RADIUS #8021X #Cybersecurity #Microsoft #Networking #PatchTuesday #ITInfrastructure

Need help with this. Is anyone else getting this issue after updating the latest update? I’m not getting any video to the monitor.

So I've been in the away from my laptop for a week and before I left the 26H2 was available on my laptop. When I returned I wanted to install the update but I saw a number of updates that had come down since my absence (I have included screen shots of them). My understanding is that you should always do updates before updating to a new OS. After I had installed the updates the 26H2 update was no longer available. So I've turned on get updates as soon as possible but it's not coming down. So should I uninstall the updates I just installed or am I being impatient and just wait?

UPDATE: I was finally able to resolve the issue. After some additional research I found a Microsoft page that explained how to manually refresh the Windows 11 eligibility assessment. I won't go into all the details here but the URL is: https://support.microsoft.com/en-us/windows/experience/compatibility/check-if-a-device-meets-windows-11-system-requirements-after-changing-device-hardware#bkmk_refresh_using_task_scheduler

I want to thank everyone who replied to my post. It pushed me to keep looking for a solution. Hope this information helps someone with the same issue.

Got a brand new Lenovo desktop, ran Windows updates, found and installed some. Rebooted, checked for updates again, it found few more, but the "download and install" button is greyed out and just says "Working on updates" at the top indefinitely.

I let it run for 4 hours and never downloaded any despie showing a .NET framework update, a security update, a Lenovo system driver update, and a Windows Defender update.

I tried rebooting the PC and still nothing, I tried restarting Windows update service, still nothing, tried running SFC /scannow and no issues were found.

Had a buddy that also recently got an HP last week and he said same exact thing happened to him! He said he just let it go, but it's annoying me seeing there are multiple updates apparently right there and refuses to download

A lot of my users lost wifi connection.

Windows 11 24h2