I lost my previous message due to forum giving me an 500 Internal Server error when replying. Each time. I had to wait a few days for it to go away.

From your Info link the command isn't setup_var3 but setup_var_3 (written in several places).

The second statement is incorrect - all of them didn't work, but only the first one said that it did work, but in reality it found two variables, managed to change one, failing to change the other and then it thought of it as a full success for some reason. To reiterate - all of them fail, only in the one case it "fails silently".

A few days? Sometimes server is down, but usually only for a few minutes. However, I am not here often in the day/afternoon, so maybe I miss longer down times? @Fernando - this isn't ever extended periods of downtime correct?

Thanks for the heads up on var_3, I never noticed until you mentioned! So, did the var_3 work or fail too?

For the one that shows you two, the second one it gives is the real variable's value, so if you see your set value there then it's changed.

It didn't work for about an hour, which is the same for me as it not working for a day so I said to myself I will try another day, and then I forgot.

Anyway, didn't try var 3 yet, but I don't thing the real value has been set for 0x79. Because that is UEFI -> Legacy Bios, and I would see the result of that in Bios or during startup. Because the EFI grub wouldn't run under Legacy Bios. I really should be trying to edit that value last. ;)

So I have used the OUVEwhatever thing, and this is the list of variables I got from it:

https://mega.nz/#!98xDiYjT!kWQbrqysUnymY...1L-7Ad27y3BnCDQ

I don't really know what to change. But my guess is that is it not a full list of variables. With my usual luck, that is. :(

Thanks @Templayer - did you try all three versions of H2OUVE? I will check this and the setup IFR and let you know what to change if we got valid output on the vars.txt - * Edit, yes that is complete and valid vars.txt! I will get back to you soon

Thanks @Fernando - I've only seen it for few seconds maybe, very rarely, but good to know it's not down hours at time often! Seems Templayer happened to catch that downtime you mention, and then maybe some other shorter one later and thought it was still down.

* Edit - Here is modified vars.txt @Templayer - put this in folder with the same version H2OUVE you used before to make the original dump you posted above, then program back in using command below
H2OUVE.exe -sv varsM.txt

http://s000.tinyupload.com/index.php?fil...806378511149227

Then dump again to compare with modified to make sure it went in (If you aren't sure how to compare, upload the varsmodcheck and I will check it for you)
H2OUVE.exe -gv varsmodcheck.txt

I would also like to note that after outputting the vars, the computer started making INSANE and LOUD noises. Windows kept working, except for the keyboard - which wasn't working.
I tried restarting the computer - the computer didn't fully shutdown, with a black screen (the sounds still going on!) and the power button not working at all (holding it, of course).

Then I've looked briefly through the manual, found a miniature pin button, had to find a needle because that was literally the only thing that would fit the "protective hole" and did a "hard" shutdown using it.

All that just due to READING the variables.
I hope the laptop doesn't outright explode when I'll WRITE the modified variables! :D

Can't be related I would image, this only dumps text from registers in memory, I've never heard of anything like that from dumping this kind of info using many different tools over many years.
Reboot, or remove power, sounds like you reset the CMOS, best to reload optimal defaults in the BIOS now.

Applied, and the new outputs matches your modifications!

I have managed to successfully boot to a ten year old Hiren's Boot CD through USB bluray drive! (and the keyboard works there. Why is this important? Read further...)

Thank you so much!

Now let's see what else blows in my face.

Also the second output had the exact same effect as the first one - weird LOUD noises and non-functional keyboard.
Also, I am now incapable of going into Bios, since it asks me for the supervisor password and the keyboard doesn't work for that prompt. It might be that the keyboard is UEFI booted or something? :D

And for anyone else reading this - the newest version of the H20UVE thing didn't work for me at first, that one has only three files (and one of them is an example batch file), so what I did is that I have looked into an older version that had many more files, and moved those files to the newer one without rewriting them. Then the newest version started working. Had to use the preinstalled OEM Win10 (UAC turned off, LUA turned off in the registry, uninstalled the crappy Norton antivirus that came with it, disabled Microsoft Defender because it is garbage...) and cmd (as an administrator, of course) with it.

And of course it did.

The keyboard at the supervisor prompt actually works, for a few seconds. Then bios freezes. Always. I have made it into it and I cannot see new options.

Win7 installation fails due to me "not having" ACPI compliant bios. :(

Funnily enough, I got into Windows XP. xD

The mini-Windows XP on Hiren's boot CD originally game me the same BSOD, but with the added note that mashing F7 during "installation" will get around the ACPI error. So I mashed F7 during booting and it did get into WinXP!

For Win7 it unfortunately doesn't work that way.
The installation flash drive I have has NVRAM (or whatever drivers for the m2 or whatever that is called SSD slots are) / SSD / updates etc. slipstreamed into it. It's 64bit Ultimate, with all the good patches.

From what I have read on the internet, people are setting ACPI settings in the BIOS to "Windows 7 compatible". Of course I cannot do that. Help? :(

That is funny about the sound, maybe some audio driver conflict with the loading or unloading of the driver/services used by H2OUVE? It's a new one to me
Newest version is not always best, and I asked you to download and run them all. Do not move files around in program packages, this may be why you're having the audio issue, or may also be why this has failed. Why did you think that was a good idea, without even asking anyone for input?

Our goal here is not mainly to allow you to see any new options, that's only a possible bonus, we are changing two default setting values, that you can't see as options in your BIOS (and wont after the change either)

You'll have to ask this user in one of his threads or via PM for advice on your ACPI stuff.
u10321_XPLives.html

So, after all that, I am lost. Did the settings get applied now and you can now install Win7 once you figure out the rest? Can you enter BIOS now? If not, we can revert back to original vars.txt, use same write command but use first backup of vars.txt as your write source.,
Then I can make you new vars, with only the one setting changed >> Boot Mode to Legacy. And then leave the Secure Boot Mode to it's default, sicne I think you can change that one in BIOS. And put the user access level back to it's default.

Here is that new vars.txt with only the single change instead (Boot mode to legacy).
http://s000.tinyupload.com/index.php?fil...180627969346606

Before using this, re-write your first vars.txt and reboot, then put this one in. I highly suggest you redownload the H2OUVE packages and do not move files from one to another (this one is newest there 100.00.16.08)
If that's the one that didn't work for you, simple, don't use it. Use another version, but don't mix and match stuff, find one that works as it is and use that, but only write using the one that gives you valid backup output too, I mean don't just write, dump first and look at it, see if it looks good, then if yes you can use that one to write back.
https://github.com/mikebdp2/Insider_BIOS_Tools

I cannot change anything in BIOS because BIOS locks up pretty much upon entry.

I cannot revert back since I don't have much to boot into, unless H2OUVE runs under XP. :)

I'm going to check Linux distributions ... it might be the time for a change.

then redo the vars as I mentioned, then try the one I just added with the single change to legacy only. Yes, H2OUVE will run on XP, you can even use Live XP probably

I bet the issue is trying to change that to Full access the cheating way with H2OUVE instead of an actual BIOS Mod.

Did you modifications to the var include fast boot? Because it is on by default and in contrast to secure boot, I cannot set fast boot in the Bios.