Strange behaviour using the "FIXED" -tool on legacy mobo GA-X58A-UD7: 1. Creating the "FIXED"-iso, burned to DVD 2. Booting DVD, starting clean install. 3. Detecting my legacy OCZ revodrive 350. search for driver from usb-stick, used on other win 10 install. (No new driver for win 11 to be found). 4. win 11 install finds and accepts the driver (inf), but "next" says cannot use the driver after all. Now tried an upgrade using tutorial: 1. Booting good old win 10 where the revoderive 350 was installed and worked ok.. 2. Executing setup from the "FIXED"-DVD 3. A quick delete of "appraiseres", and the upgrade finished without hickups. Fine !! Question: OCZ-driver was accepted during upgrade,but not dring cleaninstall Why? Can anyone explain ? regads snofte
Maybe same scenario? https://forums.mydigitallife.net/th...rsary-update-digital-signature-question.69970
@Enthousiast You can use this : Code: for /f %%i in ('powershell "get-date -format _yyyy_MM_dd"') do set "isodate=%%i"
The UEFI update simply switched on the firmware TPM 2.0 of the CPU. Before, you had to enable it yourself in the UEFI settings.
To all: The script was fixed the other day by @abbodi1406 and it runs fine on 22483. The problem is that my main system gave up on me for real this time (in the past i always managed to solve it easily), post bios error 55 (bad memory) and can't get past it, not by putting in other (tested working on other hardware) modules nor by reseating the cpu, etcetc.... even replaced the PSU to see if the voltage was failing. Today i shifted all ssd's from the main system to the second system and waiting for a new second hand replacement mainboard (to test with) and configuring an entirely new set of hardware.
Greetings from Lima, Peru !!! Many thanks Enthousiast for the information. Do I have to download a new version? if so please let us know where we can download it from as OP still showing Ver. 2.0 Stay Safe !!!!! JCC2
All offered options in v2.0 still work, the script itself won't work on DEV channel build 22483 because of wmic missing, the fixes self still work.
Simply put to those who dont understand. Run "the fix" in any build 22000.xxx or even windows 10/8/7 etc to make the Install ISO. DONT RUN IT in the 224xx builds. Then you can run the "fixed ISO" where ever you like
wmic is referenced by statements 250 and 268 of the script. A quick and dirty workaround consists in replacing statements 250-251 and 268-269 as suggested by the post #610.