chicken Posted April 21, 2023 Share Posted April 21, 2023 Witch march 6??? 1 Link to comment Share on other sites More sharing options...
mina7601 Posted April 21, 2023 Share Posted April 21, 2023 6 minutes ago, chicken said: Witch march 6??? He is talking about the Extended Kernel, its versions are written in dates. As an example, @mjd79 is talking about March 6, 2023 Extended Kernel version. 1 Link to comment Share on other sites More sharing options...
chicken Posted April 21, 2023 Share Posted April 21, 2023 Where I can get the march 6 extended kernel? 1 Link to comment Share on other sites More sharing options...
legacyfan Posted April 21, 2023 Share Posted April 21, 2023 (edited) firefox seems to work fine with the March 6 update (up to version 112 which is the latest release now) so something has changed with the functionality of browsers recently to change that (to cause the issues that are being reported) Edited April 21, 2023 by legacyfan 1 Link to comment Share on other sites More sharing options...
chicken Posted April 21, 2023 Share Posted April 21, 2023 I use Firefox 112 on October 2022 2 Link to comment Share on other sites More sharing options...
mina7601 Posted April 21, 2023 Share Posted April 21, 2023 2 hours ago, legacyfan said: firefox seems to work fine with the March 6 update (up to version 120 which is the latest release now) so something has changed with the functionality of browsers recently to change that (to cause the issues that are being reported) Firefox version 120 isn't released yet. I assume you meant 112. 1 Link to comment Share on other sites More sharing options...
legacyfan Posted April 21, 2023 Share Posted April 21, 2023 2 minutes ago, mina7601 said: Firefox version 120 isn't released yet. I assume you meant 112. I fixed the error now 1 Link to comment Share on other sites More sharing options...
Sergiaws Posted April 21, 2023 Share Posted April 21, 2023 Detected also that Clamscan (clamSentynnel/clamwin virus scanner) crashes. That's really strange cause it works even on Windows 98. The procedure entry point shell33.SHGetMalloc could not be located in the dynamic link library SHELL32.dll. 2 Link to comment Share on other sites More sharing options...
Brickedandroid Posted April 23, 2023 Share Posted April 23, 2023 (edited) On 4/16/2023 at 9:16 AM, Saswat Tech Center said: How did this happen?! Try running any 32-bit programs. For example, you can run Notepad from the SysWOW64 folder, and then try opening the file (Ctrl-O or File -> Open...), or write some characters and try saving to a file. Those will not work at all since the open/save dialog won't show anymore after March 2023 build. Edited April 23, 2023 by Brickedandroid 2 Link to comment Share on other sites More sharing options...
Sergiaws Posted April 23, 2023 Share Posted April 23, 2023 Tried that, nothing strange happened! Moreover, in my case Office 2003 which is only 32 bits can save documents and open documents without issues. 2 Link to comment Share on other sites More sharing options...
Brickedandroid Posted April 23, 2023 Share Posted April 23, 2023 (edited) 7 hours ago, Sergiaws said: Tried that, nothing strange happened! Moreover, in my case Office 2003 which is only 32 bits can save documents and open documents without issues. Do you installed the March 2023 build? (Microsoft Office uses its own independent API, and please note that NOT ALL 32-bit programs have such issue.) Edited April 23, 2023 by Brickedandroid 1 Link to comment Share on other sites More sharing options...
Sergiaws Posted April 27, 2023 Share Posted April 27, 2023 yea, March 9 version Link to comment Share on other sites More sharing options...
Brickedandroid Posted April 28, 2023 Share Posted April 28, 2023 20 hours ago, Sergiaws said: yea, March 9 version Try Notepad from SysWOW64 folder, or Dependency Walker x86. Mine have that issue but it doesn't affect Audacity and PCSX2, which both are 32-bit apps. Link to comment Share on other sites More sharing options...
sunryze Posted April 28, 2023 Share Posted April 28, 2023 i have quite a strange issue where after installing the latest extended kernel in a vmware VM, the mouse no longer works. HID-compliant mouse and PS/2 compatible mouse both say that windows was unable to load drivers for the device (code 37) Link to comment Share on other sites More sharing options...
Scorpi0n Posted April 30, 2023 Share Posted April 30, 2023 On 4/29/2023 at 1:40 AM, sunryze said: i have quite a strange issue where after installing the latest extended kernel in a vmware VM, the mouse no longer works. HID-compliant mouse and PS/2 compatible mouse both say that windows was unable to load drivers for the device (code 37) try installing windows 7 drivers for vm 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