I wanted to follow up as I was finally able to take your suggestion. I found the image you used (I don't believe I was using the correct one) and was able to install over the top. Then I didn't realize my Insider was set to the stable build, not Canary, so I switched and I can now update my build through Windows Update. Thanks for your help!
What is this Azure Arc that boots with Server, do I need it running, and if not how can I prevent it from starting?
anyone else has problem with internet speed in build 26040 ? was a tweak: Receive Window Auto-Tuning Level : disabled
Honistly I bever noticed ther was a definite hour. But seem pretty odd that the expiration is based on absolute time not on local one Australians should protest
I have to use both open-shell and Explorer Tab Utility to make explorer usable, and it kind of ruins a bit. I often can't access folders after windows sits for a while. No chance of reaching my network shares either. Strangely, no problems at all on 26040.
didnt test it on host yet, just from hyper-v. what about startallback ? always deliver after many tests on many windows 11 / servers 25
It's the last worth 26xxx build indeed. Thanks god we have finally a working Server23H2 (which runs even on old HW, and has no expiration date) (See here and following messages by me and @Ace2 )
I have not tried it recently, when I tried startallback 2 years ago, it wasn't as good as open-shell menu. Maybe it's changed, I'll try it.
They aren't 100% overlapping SW, SAB fixes a lot of general GUI issues, while classicshell is a start menu replacement with no specific W11 target (I use it since the vista days) FYI You can use both of them, just disable the start menu feature in SAB (and keep everything else enabled), then even the good old Classic Shell will work w/o issues The same is applicable for Explorer Patcher+Classic Shell (on W11/Server11 builds where EP is working). For sure ClassicShell has at least ONE feature that I find indispensable that SAB lacks (the option to show the reboot/shutdown options when connected from RDP), then usability is similar and mostly depends on the theme you use.
Thanks but think you missed the point of the discussion. No one is confused here by the backward US date format. The point was 15 v.s. 16 not 15/9 v.s. 9/15