win32 Posted March 1, 2021 Author Share Posted March 1, 2021 11 minutes ago, SevralT said: Ok, now I need to use older version? I am working on patching a newer version of winload.exe/efi and seeing if that will work better. But for now, yes, either the previous extended kernel version, or the latest extended kernel version with updates from 2017 or 18. Link to comment Share on other sites More sharing options...
win32 Posted March 1, 2021 Author Share Posted March 1, 2021 Those with newer updates can use the new extended kernel with the ntoskrnl that has been uploaded to the folder. The vanilla ntoskrnl can still be used for now, since the patched code integrity module still does the heavy lifting for unblocking ntdll modding. Link to comment Share on other sites More sharing options...
mohsad Posted March 1, 2021 Share Posted March 1, 2021 Hi, I have 64-bit Windows Vista in vmware, and when I copy the finished files using the Windows Vista CD in system32, the death screen pops up. What should I do? Link to comment Share on other sites More sharing options...
win32 Posted March 2, 2021 Author Share Posted March 2, 2021 Please disregard what I said about updates, I thought you were referring to BSODs by "death screen". Are you running x86 or x64 Firefox? Link to comment Share on other sites More sharing options...
AndrewSM36 Posted March 2, 2021 Share Posted March 2, 2021 i hope this helps with discord... (for anyone who DOESNT know lightcord is a lightweight Discord client alternative with customizability.)if Link to comment Share on other sites More sharing options...
AndrewSM36 Posted March 2, 2021 Share Posted March 2, 2021 4 hours ago, mohsad said: Hi, I have 64-bit Windows Vista in vmware, and when I copy the finished files using the Windows Vista CD in system32, the death screen pops up. What should I do? it looks like we have similar errors... as seen in my Post above... Link to comment Share on other sites More sharing options...
mohsad Posted March 2, 2021 Share Posted March 2, 2021 5 hours ago, win32 said: Please disregard what I said about updates, I thought you were referring to BSODs by "death screen". Are you running x86 or x64 Firefox? Both firefox x86 and x64 Link to comment Share on other sites More sharing options...
mohsad Posted March 2, 2021 Share Posted March 2, 2021 5 hours ago, win32 said: Please disregard what I said about updates, I thought you were referring to BSODs by "death screen". Are you running x86 or x64 Firefox? But when I do that, the BSOD goes up Link to comment Share on other sites More sharing options...
25495k Posted March 2, 2021 Share Posted March 2, 2021 I got a BSOD after installing the february 2021 update after my virtual machine restarts, Windows cannot boot with your patched winload.exe Link to comment Share on other sites More sharing options...
mohsad Posted March 2, 2021 Share Posted March 2, 2021 Link to comment Share on other sites More sharing options...
burd Posted March 2, 2021 Share Posted March 2, 2021 (edited) 19 hours ago, win32 said: Those with newer updates can use the new extended kernel with the ntoskrnl that has been uploaded to the folder. The vanilla ntoskrnl can still be used for now, since the patched code integrity module still does the heavy lifting for unblocking ntdll modding. I can confirm your updated winload and ntoskrnl files are indeed working and palemoon.exe is showing os and subsystem as 6.1 yet it still opens, well done. Edited March 2, 2021 by burd 1 Link to comment Share on other sites More sharing options...
burd Posted March 2, 2021 Share Posted March 2, 2021 (edited) Also Logitech GHUB fails to open now, upon manually trying to do so nothing happens. Edit: Upon reinstalling i got this error, but then when i relaunched it, it started working somehow https://imgur.com/a/7F6A1Zf Edited March 2, 2021 by burd Link to comment Share on other sites More sharing options...
win32 Posted March 2, 2021 Author Share Posted March 2, 2021 4 hours ago, THK2003 said: I got a BSOD after installing the february 2021 update after my virtual machine restarts, Windows cannot boot with your patched winload.exe First error indicates that ci.dll didn't get updated; second indicates that something happened to winload that shouldn't have (that error can appear if the header checksum isn't set properly, though i did do that). nointegritychecks attribute must be set to yes in the bcd store for the Vista boot volume. 8 hours ago, mohsad said: But when I do that, the BSOD goes up Then, in that case then update level is important. As for Edge, it appears you obtained an x86 version. The x64 version does not work presently due to increased reliance on newer security/crypto APIs. 3 Link to comment Share on other sites More sharing options...
25495k Posted March 2, 2021 Share Posted March 2, 2021 3 hours ago, win32 said: First error indicates that ci.dll didn't get updated; second indicates that something happened to winload that shouldn't have (that error can appear if the header checksum isn't set properly, though i did do that). nointegritychecks attribute must be set to yes in the bcd store for the Vista boot volume. Then, in that case then update level is important. As for Edge, it appears you obtained an x86 version. The x64 version does not work presently due to increased reliance on newer security/crypto APIs. I Updated the header checksum on winload.exe and now it works 1 Link to comment Share on other sites More sharing options...
legacyfan Posted March 2, 2021 Share Posted March 2, 2021 (edited) I Am Now Posting This On Firefox 64 It Works! Edited March 3, 2021 by VistaEX 2 Link to comment Share on other sites More sharing options...
Recommended Posts
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now