D.Draker Posted October 26, 2021 Share Posted October 26, 2021 On 10/20/2021 at 7:36 PM, Vistapocalypse said: KB4489887 was a March 2019 Preview in which build 6003 was first introduced. For those actually running Server 2008 SP2, such Previews were Optional updates. I don’t think any MSFN member running Vista installed it at the time, since the build number change was not noted here until April 2019. About your BSOD: AFAIK those Win32k.sys BSODs were all attributable to applications that depended on version string “6002.” Even if you don’t use Avast/AVG, antivirus would still be my first guess. One MSFN member traced his BSOD to VMWare (see my link and read a few pages). If you can identify another program that was broken by 6003, I would be as interested as anyone. Since this seems to be the only Vista thread that new members want to read, I’ll mention that Avast solved their issue with a microupdate in June 2019. To install Avast 18.8 on 6003, I would try an online installer because the offline installer is older than the microupdate. Nah , it was a clean windows Vista SP2 (no progs). Sorry for the late reply . Somehow , I was able to boot and deleted this junk from safe mode . Yet it left numerous traces , for example inside winsxs. Again , I don't have Avast , I think I wrote it . Anyways , thanks for the explanations. Link to comment Share on other sites More sharing options...
Vistapocalypse Posted October 27, 2021 Share Posted October 27, 2021 6 hours ago, D.Draker said: Nah , it was a clean windows Vista SP2 (no progs). Fake news then. Link to comment Share on other sites More sharing options...
AndrewSM36 Posted October 28, 2021 Share Posted October 28, 2021 (edited) ok i decided to disable debug mode on Windows Server 2008. and now im back to having the bsod issue i encountered on a uefi capable laptop. all the bsod displays is a stop error code. well imma type it exactly as it is on my screen rn. yes that is literally how it displays. anyone know how to fix it. im kinda tired of using the temporary fix of using the debug mode boot option... ***Stop: 0x0000001E (0xffffffffC0000005,0xFFFFF80000C545AA,0x0000000000000000,0xFFFFFFFFFFFFFFFF) Edited October 28, 2021 by ScrapMechanicFan2016 Link to comment Share on other sites More sharing options...
D.Draker Posted October 31, 2021 Share Posted October 31, 2021 On 10/27/2021 at 3:43 AM, Vistapocalypse said: Fake news then. Narrowed down to the dreaded defender . I deleted it from the ISO (before the install) , installed this update again , no errors since. Fake ? Well , I'm not the ony one who had reported the same . Reported on April 28th, 2019 at 06:47 : Removing the Monthly Rollup relieves the problem. This machine is running Windows Defender. https://www.askwoody.com/2019/problems-reported-with-this-months-server-2008-monthly-rollup-kb-4493471/ Link to comment Share on other sites More sharing options...
D.Draker Posted October 31, 2021 Share Posted October 31, 2021 On 10/28/2021 at 1:33 AM, ScrapMechanicFan2016 said: ok i decided to disable debug mode on Windows Server 2008. and now im back to having the bsod issue i encountered on a uefi capable laptop. all the bsod displays is a stop error code. well imma type it exactly as it is on my screen rn. yes that is literally how it displays. anyone know how to fix it. im kinda tired of using the temporary fix of using the debug mode boot option... ***Stop: 0x0000001E (0xffffffffC0000005,0xFFFFF80000C545AA,0x0000000000000000,0xFFFFFFFFFFFFFFFF) Do you have this update , also ? KB4493471 . Link to comment Share on other sites More sharing options...
Vistapocalypse Posted October 31, 2021 Share Posted October 31, 2021 3 hours ago, D.Draker said: Narrowed down to the dreaded defender . I deleted it from the ISO (before the install) , installed this update again , no errors since. Fake ? Well , I'm not the ony one who had reported the same . Reported on April 28th, 2019 at 06:47 : Removing the Monthly Rollup relieves the problem. This machine is running Windows Defender. https://www.askwoody.com/2019/problems-reported-with-this-months-server-2008-monthly-rollup-kb-4493471/ For someone who dislikes OT posts, you certainly post a lot of them. I was familiar with those anonymous posts at AskWoody, and linked directly to them in my April 30, 2019 post in the relevant MSFN thread (whereas you have quoted Woody’s interpretation without using quotation marks). Whereas you claimed “I’m getting BSOD right now” October 20, the anonymous poster running Server 2008 x86 without Avast reported some UAC-related issues. In addition to Windows Defender, that system had “an old spybot search and destroy.” (SpyBot ended support for Vista in 2015.) Some Vista diehards actually upgraded to build 6003 specifically because Defender definitions have required SHA-2 for the last 2 years, and none of them reported a BSOD. 1 Link to comment Share on other sites More sharing options...
D.Draker Posted October 31, 2021 Share Posted October 31, 2021 3 hours ago, Vistapocalypse said: For someone who dislikes OT posts, you certainly post a lot of them. I was familiar with those anonymous posts at AskWoody, and linked directly to them in my April 30, 2019 post in the relevant MSFN thread (whereas you have quoted Woody’s interpretation without using quotation marks). Whereas you claimed “I’m getting BSOD right now” October 20, the anonymous poster running Server 2008 x86 without Avast reported some UAC-related issues. In addition to Windows Defender, that system had “an old spybot search and destroy.” (SpyBot ended support for Vista in 2015.) Some Vista diehards actually upgraded to build 6003 specifically because Defender definitions have required SHA-2 for the last 2 years, and none of them reported a BSOD. It is on-topic , actually ! Since this update allows the extended kernel to be installed . I mean the new version of this kernel from this topic . Before you put another label , I suggest to try it yourself . I still don't know if I'm ready to use every day , though . It made my PC a bit slower , perhaps it's just placebo , I have to test further. Link to comment Share on other sites More sharing options...
Vistapocalypse Posted November 1, 2021 Share Posted November 1, 2021 6 hours ago, D.Draker said: It is on-topic , actually ! Since this update allows the extended kernel to be installed ... The extended kernel does not require KB4493471 that you say caused a BSOD that once affected many Avast/AVG users, however it does require KB4474419. 1 Link to comment Share on other sites More sharing options...
win32 Posted November 1, 2021 Author Share Posted November 1, 2021 Changes in the latest Vista Extended Kernel release: A new function has been added to user32 in x64. This should help with newer Adobe applications. Two new functions have been added to ntdll. This will allow Windows 7 WordPad to run. That function was contributed by Ximonite. Most of the K32* series of functions have been implemented to kernel32 x86. The SetDefaultDllDirectories bug is now fixed for x86 applications. Run x86 VLC and you will see the difference. GetLogicalProcessorInformationEx is also implemented on x86, without issue. Version spoofing is now implemented. Make a file in your Windows directory named osver.ini. If you have Firefox/Thunderbird 91 or above installed, or Waterfox G4 installed, copy the path of the executable to the file and place it in brackets. Write "Enabled=1" below. Then write "FirefoxFix=1" below. Then run Firefox/Thunderbird/Waterfox. Font rendering also differs slightly with this option set on older versions of those browsers. 5 3 Link to comment Share on other sites More sharing options...
burd Posted November 1, 2021 Share Posted November 1, 2021 22 minutes ago, win32 said: Changes in the latest Vista Extended Kernel release: A new function has been added to user32 in x64. This should help with newer Adobe applications. Two new functions have been added to ntdll. This will allow Windows 7 WordPad to run. That function was contributed by Ximonite. Most of the K32* series of functions have been implemented to kernel32 x86. The SetDefaultDllDirectories bug is now fixed for x86 applications. Run x86 VLC and you will see the difference. GetLogicalProcessorInformationEx is also implemented on x86, without issue. Version spoofing is now implemented. Make a file in your Windows directory named osver.ini. If you have Firefox/Thunderbird 91 or above installed, or Waterfox G4 installed, copy the path of the executable to the file and place it in brackets. Write "Enabled=1" below. Then write "FirefoxFix=1" below. Then run Firefox/Thunderbird/Waterfox. Font rendering also differs slightly with this option set on older versions of those browsers. Steam crashes, did you manage to get it running with the new ui? Link to comment Share on other sites More sharing options...
win32 Posted November 1, 2021 Author Share Posted November 1, 2021 Just now, burd said: Steam crashes, did you manage to get it running with the new ui? Not yet. I may have to implement a lot more stuff on x86 first. Link to comment Share on other sites More sharing options...
burd Posted November 1, 2021 Share Posted November 1, 2021 (edited) 7 minutes ago, win32 said: Not yet. I may have to implement a lot more stuff on x86 first. Doesn't seem far off from working, it does open steam mostly and then crashes after 10seconds or so.Does the spoofing method on top apply to all applications i wonder, for example i write Enabled=1 and Steamfix=1? Edited November 1, 2021 by burd Link to comment Share on other sites More sharing options...
win32 Posted November 1, 2021 Author Share Posted November 1, 2021 22 minutes ago, burd said: Doesn't seem far off from working, it does open steam mostly and then crashes after 10seconds or so.Does the spoofing method on top apply to all applications i wonder, for example i write Enabled=1 and Steamfix=1? Actually, there is no "SteamFix" defined. But for Steam you could attempt "SuperWin7VerFix=1". There is also a SuperWin8VerFix and a SuperWin10VerFix. 2 Link to comment Share on other sites More sharing options...
winvispixp Posted November 1, 2021 Share Posted November 1, 2021 (edited) do you need to do the spoofing thing to more .exe files than just steam.exe? haven't tried the new ver yet but will try later Edited November 1, 2021 by winvispixp Link to comment Share on other sites More sharing options...
burd Posted November 1, 2021 Share Posted November 1, 2021 (edited) 3 hours ago, win32 said: Actually, there is no "SteamFix" defined. But for Steam you could attempt "SuperWin7VerFix=1". There is also a SuperWin8VerFix and a SuperWin10VerFix. Odd, the spoofing doesn't seem to work for me at all on any program i tried. Opera still shows Windows Vista and NT6.0 and kept throwing up popups about how it can only run on Windows 7 and above. With Application Verifier it would show up as NT6.1 and aero was working. Also i kept getting kernelol.dll is missing error so i manually placed it in syswow64. Idk if its my install or the kernelex installer is broken. Edited November 1, 2021 by burd 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