PowerShell is way slower compared to the VB engine stupid idea to replace such a good engine with a slowly managed engine new ideas doesn't mean they are actually good ideas
Well Win 10 is slower than W98 but it replaced it. That's how IT (and everything else) works in capitalism A Fiat UNO from the early 80s weighted 700kg, add electronics, car stereo, airbags, ABS and so on for 40 years and a Grande punto weights 1400kg, and the latter has a worst kilometrage than the former. Powershell is slower on a Ryzen 9 than command.com on a 286 from the same era of the fiat Uno. That's all, is matter of getting used to how thing works, or start a revolution. Usually people choose the former option.
WIM dismount seems to work alot better in 22624.1391. I was doing all this stuff trying to figure out why these winre.wim keep not unmounting and reporting it was still mounted Code: reagentc /disable powershell Dismount-WindowsImage -Path "e:\mount" -discard <---- testing powershell Clear-WindowsCorruptMountPoint <--- more testing dism /cleanup-Wim <--- and more testing powershell Mount-WindowsImage -ImagePath "e:\recovery\winre.wim" -Index 1 -Path "e:\mount" -CheckIntegrity powershell Add-WindowsPackage -Path "e:\mount" -PackagePath "F:\Downloads\22624.1391_amd64_en-us_professional_7231ca3d_convert\UUPs\SSU-22621.1344-x64.cab" powershell Add-WindowsPackage -Path "e:\mount" -PackagePath "F:\Downloads\22624.1391_amd64_en-us_professional_7231ca3d_convert\UUPs\Windows11.0-KB5023527-x64.cab" powershell Add-WindowsPackage -Path "e:\mount" -PackagePath "F:\Downloads\22624.1391_amd64_en-us_professional_7231ca3d_convert\UUPs\Windows11.0-KB5023011-x64.msu" takeown /F "e:\mount" /R /D Y >nul <---- workaround for permission issues icacls "e:\mount" /grant administrators:(F) /inheritance:e /t /c /q <---- workaround for permission issue attrib -s -h -r "e:\mount" /s /d >nul <---- workaround for permission issue powershell Save-WindowsImage -Path "e:\mount" -CheckIntegrity powershell Dismount-WindowsImage -Path "e:\mount" -Save <-- didnt seem to fully work on any of the 22621 or 22623 builds powershell "Get-ChildItem -Path 'HKLM:\SOFTWARE\Microsoft\WIMMount\Mounted Images' | Get-ItemProperty | Select -ExpandProperty 'Mount Path' | ForEach-Object {Dismount-WindowsImage -Path $_ -Discard}" <-- didnt seem to work on any of the 22621 or 22623 builds F:\Downloads\wimlib-1.13.6-windows-x86_64-bin\wimlib-imagex.exe optimize "e:\recovery\winre.wim" --compress=LZX:100 reagentc /setreimage /path e:\recovery\winre.wim /target c:\windows reagentc /enable
Does this need to have so many of the same thing? can i delete the duplicates, Also does anyone else have this entry thats duplicated? Nevermind ...I just deleted them all, i think its killer software
They really messed up the beta channel, why on earth would someone enroll in Beta to have new features disabled by default (22621) and what about the odd 22623/22624 versions.
They seem to want everyone to switch to 25309, more will switch, more will have their bug reports. This is how they recruit testers for 25309 for free
I wounder if I will still receive updates sense Im on 22623 when I switched from beta to insider. 22621 has a stupid search bug that crashes when typing S Faulting application name: SearchHost.exe, version: 623.3900.0.0, time stamp: 0x63e2fb75 Faulting module name: ucrtbase.dll, version: 10.0.22621.436, time stamp: 0xf5fc15a3 Exception code: 0xc0000409 Fault offset: 0x000000000007f61e Faulting process id: 0x0x3B00 Faulting application start time: 0x0x1D94D675FED2E4D Faulting application path: C:\Windows\SystemApps\MicrosoftWindows.Client.CBS_cw5n1h2txyewy\SearchHost.exe Faulting module path: C:\WINDOWS\System32\ucrtbase.dll Report Id: ba990b8c-8013-41bb-b848-00c12160add2 Faulting package full name: MicrosoftWindows.Client.CBS_1000.22639.1000.0_x64__cw5n1h2txyewy Faulting package-relative application ID: CortanaUI gonna try clean install
I ultimately fixed it by disabling the "Instant Hotspot" feature both in the Win11 and Samsung Galaxy S21 "Phone Link" app and rebooting... :/
so I cleaned install windows 11 used defender control to disable windows defender. but then apps take longer to start?!?!? use defender to renable defender and app respond faster.. wtf
@dsbig. I'm having the same issue. Thanks for putting 2+2 together because I was about to do a reinstall.
Is that 22623 going to be the mainstream retail branch from next month's (April) Patch Tuesday, as 22624 will replace 22623 in the Preview/beta branch? Or 22621 will remain the same as the retail branch & just 22624 replace the 22623 in the Preview/beta branch?
The latter. All will be in the 22621 Retail branch, and the Beta will continue with 22624. It's just a virtual marker anyway, not a real build.
one thing a learn that nothing is truly secured but im sure a bios update can patch this vulnerability if it can be done....and im sure does so call bad actors russia and china