Here is the generic powershell script that will download and run the windows 11 updater. The few machines I tried it on, I didnt have to deal with the update assistance
<#
This powershell script will download and run the Windows 11 Installation Assistant program from Microsoft.
If the computer meets the requirements for the Windows 11 update, after the Installation Assistant runs the machine will
automatically reboot and load Windows 11. If for some reason the machine does not meet all the requirements the script
will still download and run the Installation Assistant, which will still attempt the update but fail and reboot back
into Windows 10.
Microsoft requirements can be found here: https://www.microsoft.com/en-US/windows/windows-11-specifications
#>
$WebClient = New-Object System.Net.WebClient
# URL to Windows 11 Update Assistant
$Win11UpgradeURL = "https://go.microsoft.com/fwlink/?linkid=2171764"
$UpgradePath = "$env:TEMP\Windows11InstallationAssistant.exe"
$WebClient.DownloadFile($Win11UpgradeURL, $UpgradePath)
Start-Process -FilePath $UpgradePath -ArgumentList "/Install /MinimizeToTaskBar /QuietInstall /SkipEULA"
Heres what example on a test VM what it looked like when I ran the powershell code
Does a user need to be logged in to use this script if I want to set it via GPO? Meaning, can I set a GPO to run by computer OU with this and have it run while the PC is on and not have people logged in?
I tested this on my one Test Machine, I ran the script from Syncro without a User logged into the Computer and the update to Windows 11 ran and completed. No User logged in required
What Name did you give your Custom Field? It does require you to create the field via the admin section on your own. Just make sure you match the name to whatever you want to call it in the script.
Hello, I ran the Windows 11 Readiness script, it updated the custom field fine but I have a lot of assets with CPU before 8th gen that showed up as Ready. Those processors are not supported by Microsoft for Windows 11.
there are alternate readiness checks. The cyberdrain one should be better but I think we used a ninja modified one but both use the MS hardware readiness checker.
None of the scripts I have seen check the compat list and do a cpu check but not just on cores and frequency.
Possibly tomorrow I can look at ours which we just ran and forgot.
I briefly looked at the approved CPU list and without digging too deep, any Intel CPU 7th gen or older was not on the list. This ball parks it at, CPUs Models older than 9 or 10 years would not be compatible. For Example, 7th gen Intel’s released in 2016, 6th Gen in 2015, etc.
When I spent a good about of time looking into Windows 11 Upgrade a while back, there was ways to manually by-pass Microsoft hardware requirements with registry keys, if I recall correctly. This could have all changed in the last 6-12 months.
While the community script - (CPU Age Estimate with Error Catching) does need updating, I did attempt an automation that estimates the computer’s age by using the release date of the installed CPU as reported by cpubenchmark.net . I can try and repurpose the script for the Windows 11 compatibility CPU list when I have some time in the next week or so. The original aim of the CPU Age Estimate script was to serve as a proxy to warranty lookup, which is now natively built in, so this community script has lost much of its utility. And I think it errored out the last time I tried it for an unknown reason.
No need to reinvent the wheel guys. ‘Windows 11 Readiness’ in the script library by Jim Bluemel works well and accurately. It’s just modified version of the one provided Microsoft.
