Repeated prompt "Some information has changed" when reconnecting to mobile hotspot
Problem Description When attempting to reconnect Windows 11 to a personal mobile hotspot, the connection frequently fails to connect automatically. Instead, Windows displays the following prompt: "Some information has changed since the last time you connected. We need additional information to complete the connection." (自上次连接后，某些信息已更改。我们还需要一些信息才能完成连接。) The system forces re-entering the Wi-Fi security key every time, even though the SSID, password, and security type on the phone have not changed. Steps to Reproduce Turn on the personal mobile hotspot on the smartphone (WPA3-Personal). Connect the Windows PC to the hotspot, check "Connect", and verify successful connection. Disconnect or disable the mobile hotspot. Turn on the hotspot again later and try to reconnect from Windows. Windows fails the handshake and displays the "information has changed" prompt requiring manual password entry. Observations & Potential Causes Forgetting the network via `Settings > Network & internet > Wi-Fi > Manage known networks` temporarily resolves the issue for one session, but it recurs on subsequent reconnections. Device & OS Environment OS Version: Windows 11 Insider Preview (Build 26340.9577) Network Adapter: [Intel Wi-Fi 6E AX210 160MHz] Hotspot Device: Android 16 Smartphone Hotspot WPA3-Personal 5GHz
CRITICAL REGRESSION: Build 26200 broke Mic, Game FPS & Cursors!
System Specifications: Device: Acer Aspire 5 A515-57 Memory: 16GB RAM Storage: 2x 250GB SSDs OS Build: Windows Insider Preview Build 26200 (KB5120998) Edição Windows 11 Home Single Language Versão 25H2 Instalado em 18/07/2026 Compilação do SO 26200.9278 Pacote de recursos Pacote de Experiência de Recursos do Windows 1000.26100.360.0 Issue 1: Integrated Microphone Failure Immediately after installing this build, the integrated microphone completely stopped working and disappeared from the system inputs. The audio jack still accepts headset microphones, but the internal laptop mic is dead and undetected. Issue 2: Severe Performance/FPS Drop in Gaming Game performance has been severely crippled. In Dragon Quest X S Definitive Edition (Steam), I consistently reached 40 to 50 FPS prior to this update. Post-update, the game is heavily bottlenecked, only reaching 20 to 30 FPS. This feels like a major regression in GPU scheduling, driver compatibility, or background AI/VBS overhead introduced in this preview build. Issue 3: Custom Cursors (.cur, .ani, .ini) Blocked Applying custom cursors manually no longer works. Even after moving the custom cursor files directly into the official C:\Windows\Cursors directory, the system refuses to apply .ini, .ani, or .cur files. This feature worked perfectly prior to the update. Please investigate and fix these regressions in the 26200 flight. Attached are screenshots demonstrating the update build and the issues.WOA 29639.100 explorer.exe freeze when open some folders
When attempting to open certain folders, File Explorer's CPU usage spikes rapidly, and some or all file items become invisible. Stack traces viewed via Process Monitor reveal that the activity consistently involves the `SetLinkFlags` function shown in the image. Third-party file management tools such as File and 7-Zip operate normally, and issues related to non-system Shell components have already been ruled out by ShellExView. 7zip can show all files normally.Can we get Microsoft to make the CorePC modular OS into a windows 12 smooth experience?
Guys I was thinking microsoft should change the software architecture for windows on ARM devices since they chose to use a unified memory architecture and ram consumption is nuts, I thought we could maybe convince them into making it so that the Os they seem to be planning to make for arm devices is rlly lightweight and modular, if compatibility was an issue they could maybe make a wine-like compatibility layer that doesnt run unless the program is categorized as x64 rather than arm, like a "better prism" which is the current compatibility layer, and maybe make better use of the npu so it actually helps the OS rather than just idling there, unmenacingly, MICROSOFT TEAM IF U SEE THIS PLEASE DO I NEED THIS, THESE ARM DEVICES HAVE SO MUCH POTENTIAL BUT RIGHT NOW THEY ARE KINDA BAD PLEASEEEEEE, GET EM BOYS
New Outlook Unable to Close Since build 26220.8754 Update
Since build 26220.8754, I (and others) have been unable to close New Outlook using the X. I went into Windows Settings > Apps > Installed Apps > Outlook > click the 3 dots to the far right, select Advanced Options. Then select Reset. It worked for 1 time, but then the issue just showed right back up. I am not the only one with this issue, it has been reported here https://learn.microsoft.com/en-us/answers/questions/5933524/new-outlook-doesnt-close-with-x-any-longer?source=docsMicrosoft Print to PDF not working/missing.
The Microsoft Print to PDF was not working on my PC so I tried reenabling it via Windows Features in Optional Features and it won't turn back on. It gives error code: 0x800f0922. I also tried other various methods online and none work. All end with various error codes which all result in the service not working/turning on. I even filed feedback about 2 weeks ago with no response yet. I contacted support, where I was recommended to perform a repair via ISO but was then canceled by the agent as I am on an Insider build. I am on build 26300.8687. This is a summary of my diagnostic from Gemini which I had used to try to solve my issue. Here is a summary of the diagnostic, tracking every command I executed in PowerShell and the specific roadblocks the Windows subsystem threw back. The Add-Printer Layer attempted to use modern PowerShell commands to register the printer onto both the interactive prompt port and the standard local file port. Commands Ran: PowerShell Add-Printer -Name "Microsoft Print to PDF" -DriverName "Microsoft Print to PDF" -PortName "PORTPROMPT:" Add-Printer -Name "Microsoft Print to PDF" -DriverName "Microsoft Print to PDF" -PortName "FILE:" * **Errors Faced:** * `ObjectNotFound: (MSFT_Printer:ROOT/StandardCimv2/MSFT_Printer)` * `HRESULT 0x80070002,Add-Printer` --- ## 2. The Legacy PrintUI Layer To bypass the modern PowerShell cmdlet, I tried using the legacy Windows user interface print engine via standard command prompt syntax and escaped quotes. * **Commands Ran:** ```powershell cmd /c "rundll32 printui.dll,PrintUIEntry /if /b `"Microsoft Print to PDF`" /r `"PORTPROMPT:`" /m `"Microsoft Print to PDF`"" rundll32 printui.dll,PrintUIEntry /if /b "Microsoft Print to PDF" /f "C:\Windows\System32\spool\DRIVERS\x64\3\prnms009.inf" /r "PORTPROMPT:" /m "Microsoft Print to PDF" Errors Faced: A graphical dialog box error: Operation could not be completed (error 0x00000002). The system cannot find the file specified. The Deployment Script Layer (WMI/CScript) I tried deploying the printer using Windows’ built-in visual basic administrative scripts to side-step the user interface layer completely. Command Ran: PowerShell cscript $env:windir\System32\Printing_Admin_Scripts\en-US\prnmngr.vbs -a -p "Microsoft Print to PDF" -m "Microsoft Print to PDF" -r "PORTPROMPT:" * **Errors Faced:** * `Unable to add printer Microsoft Print to PDF Error 0x80041002 Not found` * `Operation PutInstance` * `Provider Win32 Provider` * `Description The system cannot find the file specified. Win32 error code 2` Ultimately, every single command failed with an identical variation of **"File Not Found" (Error 2 / 0x80070002 / 0x80041002)**.
