Post AKSRxWAWPkMBbihDU0 by blackfire@fosstodon.org
 (DIR) More posts by blackfire@fosstodon.org
 (DIR) Post #AKSKl8LETiKUYQqymm by brandon@fosstodon.org
       2022-06-13T19:49:17Z
       
       0 likes, 0 repeats
       
       Accidentally installed a volume activation channel edition of Windows instead of Retail/OEM and the built-in activation key isn't properly installed?`Get-WmiObject -query 'select * from SoftwareLicensingService' | Select-Object -ExpandProperty OA3x0riginalProductKey | %{slmgr.vbs -ipk $_}`
       
 (DIR) Post #AKSRxWAWPkMBbihDU0 by blackfire@fosstodon.org
       2022-06-13T21:09:59Z
       
       0 likes, 0 repeats
       
       @brandon I would save yourself the hassle and just reinstall from fresh.
       
 (DIR) Post #AKSSveF1Wt4Q1FTS4m by brandon@fosstodon.org
       2022-06-13T21:20:51Z
       
       0 likes, 0 repeats
       
       @blackfire not really an option when you’re supporting a dev who just spent 3 hours setting up their dev env after they got their laptop upgrade 😅
       
 (DIR) Post #AL8AHGoZqekLftSXaK by brandon@fosstodon.org
       2022-07-04T00:09:43Z
       
       0 likes, 0 repeats
       
       @blackfire Coming back to this a little while after, and I think this is a really bad idea and doesn't actually fix the problem. Because if you didn't have a retail/oem version of Windows on hand, then you'll just be wasting your time downloading a new copy of Windows, reinstalling Windows, and then setting up windows...whereas this is like...a single line of Powershell?