builtbybel / builtbybel/FlyOOBE
[feature] Prevent FlyBy11 running on old CPUs
- Dominant language
- C#
- Stars
- 7.3k
- Forks
- 379
- PR merge metrics
- No merged PRs in 30d
Description
I tested FlyBy11 with 24H2 ISO on an Acer Aspire 5930G (Core2Duo P9600, 4GB, SSD, Geforce 9800GT).
I am a regular user and yes I didn't read the readme until the end. I read until old outdated PC and thought FlyBy was some kind of graal.
The end of the readme says that it won't make possible bypass POPCNT and cpu that does include it are from 2010 and P9600 clarily doesn't have it.
So I wasted time (I love wasting time) and SSD write cycles.
So why FlyBy11 doesn't check the CPU and says "the cpu of this PC doesn't have POPCNT" ... SSE4.2... and user will not use the program.
23H2 can be used without Popcnt/SSE4.2... so FlyBy will need to check the CPU string and ISO being installed and prevent users from install 24H2 on Core2Duo/Quads and below that.. maybe first Core gen i3/i5/i7.
Because of MS's move... I can not use 24H2 can't be installed on the laptop mentioned above. I can install 23H2 but there is a strange bug affecting usage with nvidia graphic cards. The screen when goes standby and comes back by moving the mouse.. we will just get a frozen screen and the only way we can get the screen back is to use ctrl+al+del.. and obviously rebooting as well.
So make FlyBy check the CPU and the ISO being installed. IF 24H2 ISO and CPU doesn't have POPCNT, abort.
CPU string can be accessed by WMI and probably some other way.
The ISO can be mounted and maybe check the setup.exe's (and some other exe) version. 26100+ being 24H2.
Also no one will click those links where it says to drag the ISO over.
I think it's not possible to determine the windows version from ESD/WIM indexes.
Thanks.
Contributor guide
No contributing guide indexed for this repository
Assessment
This issue has not been assessed yet.