Correct me if I'm wrong, clear.exe its just making your window to be transparent I think. (I think, I saw FBConan use clear.exe on their new Quantum Leap win11 lite video)There is a clear.exe that is running on startup. Dont know where it came from - OS may be. Could some one clear my doubt about clear.exe please.
@ophie I adjusted the size of the HD in Virtualbox to just 256G. Now this installed successfully. Before I was using 2T.
Clearexe is on every Phoenix build, It makes windows transparent. in earlier builds, it's enabled by default, but in recent ones, FBConan disabled it by default, and let the user enable it if he wants transparency. In previous builds, the description re Clearexe is in the OP, apparently he forgot to mention that on this build.There is a clear.exe that is running on startup. Dont know where it came from - OS may be. Could some one clear my doubt about clear.exe please.
I don't think it is Virtualbox's fault. I've been using 2T disks for long time, both with Windows and Linux under Virtualbox.
So Virtualbox doesn't understand terrabyte drive? Anyways, good you were able to resolve the issue.
Sorry for the late response,. I haven't log in in a while. Yes, it worked for me and the beginning of my statement is "it works in this rendition". That means this release 22621.675. I used a non-signed sound driver to have Dolby in my PC. To install it I have to follow the process I posted.Not working buddy, did you tried to do the same with this build?
For me, it's not even booting to the Startup Setting.Sorry for the late response,. I haven't log in in a while. Yes, it worked for me and the beginning of my statement is "it works in this rendition". That means this release 22621.675. I used a non-signed sound driver to have Dolby in my PC. To install it I have to follow the process I posted.
Touchscreen works for me, if that's what you're asking...hello, will this include tablet mode? I have a 2-in1 laptop.
Good, I am glad you got it solved. Something that I just thought about is you would not happen to have fast boot active in your BIOS/UEFI settings?. I know that in some motherboards it will negate/cancel any availability of Windows OS boot options.For me, it's not even booting to the Startup Setting.
it's just restarting my PC whenever I choose to boot into it from Advanced Startup.
but the other method is working which is mentioned by @ophie!
Fastboot wasn't active.Good, I am glad you got it solved. Something that I just thought about is you would not happen to have fast boot active in your BIOS/UEFI settings?. I know that in some motherboards it will negate/cancel any availability of Windows OS boot options.
Is there a noticeable difference between the two builds? is it worth the leap?Fastboot wasn't active.
Btw, I just switched to newer build Quantum Leap!
Yes, I can now enter startup settings, but when I press the F7 key to turn off driver enforcement, Windows boots up instead of disabling it.Is there a noticeable difference between the two builds? is it worth the leap?
When you select F7 in the boot menu Windows boots up normally and there is nothing different other than now when you try to install a unsigned driver it gives you a warning but allows you to install it. Again, there is nothing different in the boot process after you select F7. It will look like a normal windows boot, login..etc.Yes, I can now enter startup settings, but when I press the F7 key to turn off driver enforcement, Windows boots up instead of disabling it.