[34508795] (OneDriveCard) Priority : Service (4) State : Enabled (2) Type : Override (0) [40733296] (UnifiedStorageQuota) Priority : Service (4) State : Enabled (2) Type : Experiment (1) restore onedrive info card under accounts with new storage quota UI Cant find the id for the office info card, if anyone knows it please post incase anyone didn't get this enabled after update [38228963] (AdminFlowRejuv_RenamePC) Priority : User (8) State : Enabled (2) Type : Override (0)
Maybe WaaSMedic reinstall it? disabling ContentDeliveryManager never worked well for me, i usually unregister it during setup https://forums.mydigitallife.net/posts/1335997/
was wait for 22624 RGB lighting control awesome. vivetool /enable /id:35262205 vivetool /enable /id:41355275
I found that even after installing Windows.Client.WebExperience_423.5500.0.0 manually, the system still removes and installs 423.3400.0.0 In addition, disabled WaaSMedicSvc and Task Scheduler seems to have no effect.
use winget to uninstall it and manually re add winget uninstall "Windows web experience Pack" im running dev build of web experience pack, no issues
I was running 22623.1325, and applied the updates using W10UI. Now on 22624.1391, and so far everything looks good.
freshen install 22624.1391 and saves lots of headaches no more ASUS,EVGA LIAN-LI software win 11 handles it very well
Since people think that: 95 - Bad 98 - Good 2000 - Bad XP - Good Vista - Bad 7 - Good 8 - Bad 10 - Good 11 - Bad then MS knows that they'll think: 12 - Good
sounds like you've got in-place upgrade to the Retail channel as it was described here https://forums.mydigitallife.net/posts/1778538
bad in the sense that win11 kinda runs slow on "old" PCs with old hardware but win11 runs fine on modern hardware with recent superfast ssds
[/QUOTE] A cleaned Win 11 runs on old HW not any worse than Vista/7/8/10, the problem is that when it runs you get the uglier cousin of Macos, which is ugly on it own.
Finally fixed my inplace upgrade issue. My Samsung NVME Controller was being seen during the upgrade as a Dell Perc S150 which are both. PCI\VEN_144D&DEV_A808 but the subsys is different. Caused inaccessible boot device errors. Anyway, deleting the dell perc oem.inf fixed the problem and inplace upgrade to 22624.1391 worked well. Code: Microsoft Windows [Version 10.0.22624.1391] (c) Microsoft Corporation. All rights reserved. C:\Windows\System32>
I have a laptop ASUS K551LN 8GB of Ram, if I do a clean installation of win 11 it takes a long time to load so I restore it to Factory that brings win 8, then I upgrade it to Win 11 and it loads much faster, I think it's a matter of drivers since in this way it maintains the original ones that came with Win 8 and if you do a clean installation it changes them for other Windows ones
so according to the news MS plan to kill the VBScript engine so now what? move to slowly PS instead? they was having the plan to kill wmic, and now vbs on the line, what about the activation tools ? slmgr.vbs ? ospp.vbs ? they will stop working? wonder how deep this rabbit hole is going
Dism & Powershell command to restore it (will add this check for next rtool version) Code: DISM /Online /Add-Capability /CapabilityName:WMIC~~~~ DISM /Online /Add-Capability /CapabilityName:VBSCRIPT~~~~ Get-WindowsCapability -Online | ? {$_.Name -Match 'Wmic|VBSCRIPT' -And $_.State -eq 'NotPresent'} | Add-WindowsCapability -online for %%# in (VBSCRIPT,WMIC) do ((DISM /Online /Get-CapabilityInfo /CapabilityName:%%#~~~~ | >nul 2>nul find /i "State : Not Present") && DISM /Online /Add-Capability /CapabilityName:%%#~~~~)
Windows is plenty of shells, partly redundant, on what they do. Think to netsh, it made some sense when cmd was in charge, but now that PS is the jack of all trades, netsh makes little sense. Then we have diskpart, ntdsutil and alike that could (and likely will) be replaced by PS commands/commandlets. In short, potentially, the rabbit hole is very deep