Forum Widgets
Latest Discussions
For those with Windows Insider Problems to read please before posting in this Server Insiders Forum
For all Windows Insider Build issues Home, Pro, Pro for Workstations, Etc. the Windows Insider Forum is https://learn.microsoft.com/en-us/answers/tags/953/windows-insider Respectfully meaning to be helpful Thank You p.s. Can Microsoft please lock this conversation topic as closed and if possible pin it?
26063 deduplication data corruption is still there.
From Server 2022 up to this newest 26063 build, they all have the same problem, as described here: https://techcommunity.microsoft.com/t5/windows-server-insiders/server-vnext-26040-and-server-2022-deduplication-data-corruption/m-p/4047321 I am out of energy for today and give up for today. It seems to be impossible to get Microsoft to care for actual OS bugs instead of marketing.
Problems to join Debian/Ubuntu machines to a domain
Is not posible to join Debian/Ubuntu machines to a domain based on Windows Server 2025 (using realm at least) this is the error: ! Couldn't set password for computer account: XXXX$: Message stream modified adcli: joining domain xxxx.local failed: Couldn't set password for computer account: XXXX$: Message stream modified ! Failed to join the domain realm: Couldn't join realm: Failed to join the domain Domain is discoverable vía realm: root@lnms01:/home/administrator# realm discover xxxx.local xxxx.local type: kerberos realm-name: XXXX.LOCAL domain-name: xxxx.local configured: no server-software: active-directory client-software: sssd required-package: sssd-tools required-package: sssd required-package: libnss-sss Tested on WS2025 build 26227 and Linux 6.1.0-21-amd64 x86_64, Linux 6.6.31+rpt-rpi-v8 aarch64 and Linux 6.8.0-31-generic x86_64. Those 3 versions of Linux joined to another doman based con Windows Server 2022 without issues.
Unable to download Windows 11 Client Arm64 Insider Preview Dev Channel Edition
Error We are unable to complete your request at this time. Some users, entities and locations are banned from using this service. For this reason, leveraging anonymous or location hiding technologies when connecting to this service is not generally allowed. If you believe that you encountered this problem in error, please try again. If the problem persists you may contact page for assistance. Refer to message code 715-123130 and c21934f3-66c0-43e3-9e88-c5869adeae48. I am in the US and simply want to download this. Please provide a usable link without restrictions.
Can't roll-back from 25h2 to 24h2.
A few days ago, my PC automatically updated from version 24H2 to 25H2, and ever since then, I've been experiencing persistent issues that I haven't been able to resolve. Unfortunately, the option to roll back to the previous version seems to be unavailable, which has made troubleshooting even more difficult. I've tried just about everything I could think of—tweaking settings, running diagnostics, checking for compatibility problems, and even reaching out to support forums—but nothing has worked so far. It's been incredibly frustrating, and I'm still stuck with the same problem.
Microsoft Store Error – “Sorry about that! Something went wrong, but we are making it right.”
Hello Insider Community, I’m currently experiencing a persistent issue with the Microsoft Store on my Windows device. Every time I try to open the Store or update apps, I receive the following error message: > “Sorry about that! Something went wrong, but we are making it right.” This has been happening consistently, and clicking “Refresh” does not resolve the issue. I’ve already tried the following troubleshooting steps: - Resetting the Store cache using `wsreset.exe` - Repairing and resetting the Store via Settings - Re-registering the Store using PowerShell - Verifying time, region, and account settings - Running SFC and DISM scans - Restarting the Microsoft Store Install Service Despite these efforts, the error persists. I am signed in with a Microsoft account, and my internet connection is stable. I’m not using a VPN or proxy. I’m currently on [WINDOWS 11 HOME SL, INSIDER BUILD DEV CHANNEL] Any guidance, known workarounds, or confirmation of this being a known Insider build issueDomain Controller showing network connection as Public
Notice for quite awhile now with the vnext server builds that when you promote it to domain controller it shows the network connections as public or private instead of DomainAuthenticated. Is there a networking piece that I am missing that needs to be configured
