so? I installed it this spring and it's fine you can expect everything from OEM crap, I remember some builds were completely blocked on all ASUS motherboards any shell customization software, MSFT doesn't like that stuff
Then i can only assume the pro on the server is used for some reason like a MSDM for Pro on the system? I have never used MDT so i can't tell
So, what? What does that have to do with what I said? Then that contradicts what you said about the modern systems having lower failure rate. Where did you read that information about shell software, by the way? Also, after all 24H2 was released (even if not in WU) 3 days ago or not?
Or maybe you don't pay attention to what I say and because of that you say things that don't have to do with what I said, not to mention you contradict yourself and assume some things are common sense. You're not forced to reply me, by the way. What about yours?
24H2 takes a lot of time to install and now I have to choose the second Volume during the install to proceed because for some reason the new one is no longer default, which is annoying.
24h2 version forgetting window position as well... unattend driver from autounattend file is listed but not install... no idea what microsoft have done
what does it even mean? window position of what exactly? I lust tried Edge, File Explorer, foobar2000 - everything is fine as usual
there is an option for multi monitor setup in windows settings (system -> display), it's off on my system, no idea why, check it there works fine with the one monitor, turned it off and on and the window is on the same place
it happen with scalling enable... 4k monitor with 150 scalling... 23h2 is fine... only happen with 24h2
my scaling is also 150% at 2160p, but I only have one monitor so can't say anything about multi monitor setups
Yes, but take official 26100.1742 ISO and apply 26100.1882 update using abbodi's W10UI (10.46-rc). Install the image, run SFC Scannow to see that it is corrupt, but SFC Scannow also reports that it repaired with success. It did not. Corruption was found each time SFC Scannow was performed. Official build 26100.1742 ISO is also corrupt when verified with SFC Scannow, but is can be repaired, unlike build 26100.1882.
What is the recomended setting in 10.46-rc? I ran it ond only change clean up the rest is untouched but would like to know the recomended setting hopefully with out error. thx.
my config is this Spoiler Code: [W10UI-Configuration] Target = Repo = DismRoot =dism.exe Net35 =0 Net35Source = Cleanup =1 ResetBase =1 LCUwinre =0 WinRE =1 UpdtBootFiles =1 SkipEdge =0 SkipWebView =0 UseWimlib =1 _CabDir =W10UItemp MountDir =W10UImount WinreMount =W10UImountre wim2esd =0 wim2swm =0 ISO =1 ISODir = Delete_Source =0 AutoStart =0 AddDrivers =0 Drv_Source =\Drivers requires wimlib in bin or bin\bin64 folder in bin folder I have cdimage.exe and PSFExtractor.exe
Same result. File integrity for 26100.1882 ends up permenantly damaged, not fixable, even though SFC Scannow reports that it fixed all corrupted files. Reboot and SFC Scannow finds corrupted files again. Normally you can figure out what files are corrupt using CBS Log, but not this time. It does not list which files are corrupt. Are there tools/apps that can interpret DISM logs and CBS logs to tell you exactly which files are corrupt? The calming part of all this is that both file integrity and component store verification are overrated. They are simply side by side checks. Having corrupt store and file integrity does not mean that anything is corrupt. SFC Scannow is also out of sync with DISM when components are removed. SFC Scannow restores files for some removed components and those files are never used.