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)**.
Feature not available on Windows Dev build 29576.1000
I am currently on the Windows Dev version (build 29576.1000), and the feature is not available for me. I would like to ask whether this feature can be enabled on my device, or when it will become available for this build.” (Full Screen Experience)
Windows 11 build 26200.8116 broke system dll crtdll.dll
Latest Windows 11 25H2 release broke this system dll by replacing it with msvcrt40.dll which isn't anywhere like it, and it broke 32 bit programs that relied on that dll to run since it is missing symbols. I couldn't find an appropriate space to report this kind of issues, since this is not user error or a configuration problem, but a bug caused by a windows update that only has meaning for developers and users which use the very few apps remaining relying on this component. If there's a better way to report this issue, let me know, but I have no direct access to a Windows 11 device so i can't use the feedback hub applicationWindows 12 Is Not a Rumor. It’s Already in Your System
The new build 29558 reveals way more than most people think. If you know where to look, you’ll see that the next Windows release is already very close. Side‑by‑Side Winners now includes new versions of core system modules Startup‑task‑data is updated across all architectures Defender and Networking UI have new branding resource packages ShellCompatibility is already using version 12.\* GDI+ and the Search engine have new generations of libraries These are not “small tweaks”. This is the groundwork for a new shell and a new UI that is already physically present in the system — just not unlocked yet. Don’t follow YouTube “tech enthusiasts” — they spread rumors and don’t know how to look for real evidence inside the system. Windows is not analyzed through thumbnails, but through the registry, WinSxS and shell layers. 😎✌️ Winners sample: offlinefiles-ui is now running on version 29558.1000. This is one of many modules that indicate the presence of a new shell layer in the system.Native Vulkan in Windows System Manifest
Vulkan’s been in Windows for ages as a loader and runtime, but the OS still doesn't use it as a native backend. It's wild because so many studios start with Vulkan now and only port to DirectX later, which just adds a ton of extra work for no reason. If Windows actually supported Vulkan natively, we’d get rid of those translation layers that cause CPU overhead and shaky frame times. In CPU-bound games, we’re talking 20–30% more performance just by cutting out the middleman. Plus, it would mean consistent performance across NVIDIA, AMD, and Intel. I really think Vulkan should be a priority in Windows, not just an add-on. What do you guys think? Is it worth pushing Microsoft on this, or are they too locked into DX12?" Community Call to Action If you believe Windows deserves a modern, efficient graphics backend — If you’ve ever seen performance lost to translation layers — If you want Vulkan to be treated as a first-class citizen inside Windows — Then speak up. Share your thoughts. Test, compare, and challenge the status quo. This isn’t just about games. It’s about the future of UI, recovery, and system performance. Let’s show Microsoft that the community is ready for native Vulkan. No translation. No compromise.
installing Windows while keeping all your files and apps intact
I have been facing an issue in Windows OS that my major apps are crashing, and windows is not all responding normally. I an in insider preview build of Windows and this has been happening since yesterday after I installed the latest Insider Preview Build. Now when I decided to go back to previous version I was not able to and decided to install normal windows 11 ( public release ) and disengage from insider program but after installing the ISO file and running with all apps and files to be intact after a while the blue screen came to install windows , after which it logged me back to my home screen stating that their was some error installing windows 11 So if any of the moderators could help me with this ASAP
New laptop problems with system
Hello, i have this problem on new bought laptop that is completely brand new. I updated Windows and it happened. So what happened? After opening Windows, logging in my screen looks like it’s constanly refreshing. There is no way to open anything or go into settings. Only way to open cmd is via task manager which Works. Even after trying a few cmd options and then uninstalling updates it’s still like that. (Constant refresh) when turned in safe mode same thing. Even in „tryb awaryjny” it’s still the same. I tought maybe uninstalling latest feature update will help but i cannot do that. this laptop has like 5 days so pls help me cuz im losing it
