But you've really done enough “advertising” for your ISP now. Are the articles for tonight,Patch Day, already prepared?
@Enthousiast Yes, TrueNAS is really tempting running with ZFS. Also in my Wishlist for local NAS server. Those chinese mini 'ultra specs' x86_64 PC on aliexpress is really nice from the specs for running TrueNAS, although I kind of worried about 'hardware backdoor'. They even have 25 Gbps sfp+ supports!. My x86_64 Intel Icelake OpenWrt main router is directly imported from aliexpress, been running it for the last 6 years, no noticeable issues so far, rock solid enough for me. I wonder if 26H2 build is stable enough for constant 10 Gbps backup transferring to NAS.
I'm pretty happy with my (cable) connection. 1000 / 50 for €50.00 a month, including phone and TV. Fiber optic service has been available in our neighborhood since last week. I'm not sure yet if it's worth switching. (My “heavy user days” are actually over, right!? Although I sometimes have my doubts about that. ) And so far, my current connection has been enough for my needs. The upload speed could be higher, but with cable, the maximum here is only 75 Mbit/s. oO ....
Yeah, the cable connections here are now going to offer 8Gbit/s down and max 350Mbit/s up but they say this could be 10Gbit down and 6Gbit up in the near future, i need the same upload as download (fiber) because my heavy user days are still very alive
Yes, you can “really” work with that. Things are a bit different in Germany, but I don't want to complain too much. Some things take longer, while others go surprisingly fast. It has a lot to do with the structure of our 16 federal states. It can be complicated at times.
windows11.0-kb5127648-x64.msu fail on windows 11 26H2 when installing and got error when update by windows i saw download last 09 security update (although it installed before) what is the problem?
Does MS have a preview update schedule? Isn't it supposed to be on Thursdays 2 days after Security--2nd-Tuesdays and again 2 weeks later? Also, will LTSC 24H2 get preview updates? Non-LTSC 24H2 is EOL, except for LTSC, but does that include previews or security-only updates (for LTSC 24H2 that is) ?
It was whenever they decided to in the past edit: i read insider preview, preview should be 4th thursday, iirc (week d). With 2021 LTSC they stopped including the 2021 LTSC SKUs from receiving preview updates when 22H2 became retail channel, but they still can be installed manually.
Somehow I think a brilliant security researcher is going to exploit this feature in another 2-3 years.
Windows Insider Canary Build 26340.9750 – Explorer.exe crashes on sign-in, leaving desktop unavailable Category: Windows Insider Program → Desktop Environment / File Explorer Affected build: Windows 11 Insider Preview 26340.9750 Previously working build: 26340.9616 Date: October 16, 2026 Affected machines: DELTA-V11 and DELL-14 1. Problem description After installing Windows Insider Preview build 26340.9750, the Windows desktop fails to appear after signing in. The issue has been observed on two separate computers, DELTA-V11 and DELL-14. On DELTA-V11: The desktop and taskbar do not initialize successfully. Ctrl+Alt+Delete remains functional. Task Manager can be launched. CMD and PowerShell 7 can run, including with administrative privileges. Manually starting explorer.exe causes the process to terminate after a few seconds. The issue occurs with different user accounts. Removing the previously configured HKCU\Software\Microsoft\Windows\CurrentVersion\Explorer\Serialize registry key and restarting Windows did not resolve the problem. 2. Application crash details Windows Application Event Log, Event ID 1000: Field Value Faulting application Explorer.EXE Application version 10.0.26100.9750 Faulting module SettingsHandlers_DesktopTaskbar.dll Module version 10.0.26100.9750 Exception code 0xc0000409 Fault offset 0x000000000003a274 Module path V:\Windows\System32\SettingsHandlers_DesktopTaskbar.dll Repeated crashes were recorded on October 16, 2026, at: 20:03:59 20:06:08 20:06:39 20:22:56 All four events identify the same faulting module, exception code and offset. The exception code may indicate a fail-fast termination. Its precise cause has not yet been determined. 3. Attempted rollback and servicing failure The installed cumulative update package was identified as: Package_for_RollupFix~31bf3856ad364e35~amd64~~26100.9750.1.4 KB: KB5127842 The previous package, version 26100.9616.1.1, was listed as superseded. The initial rollback attempt used: Remove-WindowsPackage -Online -PackageName 'Package_for_RollupFix~31bf3856ad364e35~amd64~~26100.9750.1.4' -NoRestart The operation failed with: Permanent package cannot be uninstalled due to container dependency. CBS.log reported: Container base layer depends on LCU version greater than '10.0.26100.9750'.: 800f0926 CBS_E_CANNOT_REMOVE_CONTAINER_DEPENDENCY The rollback was therefore blocked during CBS dependency validation. Additionally, DISM /Online /Get-OSUninstallWindow returned error 2 (file not found). Windows Recovery Environment was not available on this particular machine due to a separate pre-existing issue. 4. Successful workaround The following optional Windows features were disabled from an elevated PowerShell session: Disable-WindowsOptionalFeature -Online -FeatureName Containers-DisposableClientVM -NoRestart Disable-WindowsOptionalFeature -Online -FeatureName Containers-Server-For-Application-Guard -NoRestart After a complete system restart, both features were confirmed as Disabled. The same Remove-WindowsPackage command was then executed again. This time, the previous immediate container-dependency error did not occur, and the rollback completed successfully. After restarting, DELTA-V11 returned to: Microsoft Windows Version 10.0.26340.9616 The normal desktop and Windows Settings interface were restored. This strongly associates the desktop failure with the installation of build 26340.9750, although the exact root cause remains undetermined. The successful rollback also suggests that the enabled container-related features contributed to the servicing dependency preventing update removal. The individual contribution of each feature was not isolated. 5. Expected behavior Explorer.exe should initialize normally after signing in, presenting the desktop, taskbar and notification area. The system should also support removal of an uninstallable cumulative update without unexplained container-layer dependency failures. 6. Actual behavior Explorer.exe repeatedly terminates during desktop initialization. No usable Windows desktop is presented. The issue is not limited to one user profile. The initial rollback attempt fails with CBS error 0x800f0926. Disabling Windows Sandbox and Container Server, followed by a restart, allows rollback to proceed. 7. Request to Microsoft Please investigate: A possible regression in SettingsHandlers_DesktopTaskbar.dll version 10.0.26100.9750, particularly around offset 0x3A274. The repeated Explorer.exe fail-fast exception 0xC0000409 during desktop initialization. The CBS container base-layer dependency check that prevents removal of KB5127842 while the specified container-related optional features are enabled. Whether these issues are known in Windows Insider Preview build 26340.9750. Application Event Logs, CBS.log extracts and additional diagnostic traces can be provided if required. Additional observation: A second computer, DELL-14, exhibits the same missing-desktop symptom after updating to build 26340.9750. The exact faulting module and exception details have not yet been confirmed on that computer.