Jump to content
MSFN is made available via donations, subscriptions and advertising revenue. The use of ad-blocking software hurts the site. Please disable ad-blocking software or set an exception for MSFN. ×


  • Content Count

  • Joined

  • Last visited

  • Days Won

  • Donations


win32 last won the day on January 1

win32 had the most liked content!

Community Reputation

662 Excellent

About win32

  • Rank
    You will own nothing, and you will be happy
  • Birthday 05/24/2001

Profile Information

  • OS
    Vista Ultimate x64
  • Country Flag CA

Recent Profile Visitors

7,462 profile views
  1. I am unable to replicate any complications caused by sfc /scannow. I ran it then rebooted as prompted. Extended kernel files were replaced with the previous MS files. Then I installed the extended kernel and rebooted. The extended kernel files were present again and no issues were present.
  2. Not even one reboot after running sfc does the installer work?
  3. This "Universal Theme Patcher" is what I used: https://cdn.discordapp.com/attachments/447531495062503456/556252683569332246/UniversalThemePatcher_20090409.zip
  4. That probably happens because you ran the installer more than once in an OS session. The in-use system files are renamed while the new ones are copied to their old positions. Before rebooting, the renamed files are the ones that remain in use, so they are untouchable. You do have April 2017 updates, right?
  5. Yes, my custom uxtheme is patchable. Indeed I believe that the one I've included has been patched.
  6. The original installer script did not take into account those with usernames containing spaces. I have since adjusted it to work with such usernames.
  7. I'm not sure about it, as it seems that .NET is a bit of a black hole as far as Vista is concerned. Versions 4.6.2 and above have some antipathy to Vista in some way, and I have trouble figuring it out.
  8. No, unless MS recognizes the extended kernel files as "legitimate" and grants us the use of their authenticode signatures to sign them.
  9. I haven't figured out how to get the Steam browser to work yet, though Chrome x64 and Firefox x64 should work easily if extracted from the installers (for the latter anyway) or downloaded as portables. Not sure about Adware...
  10. The DLL is signed only as SHA-2, but I don't believe that is the reason as Vista doesn't normally block execution of user-mode code with "invalid" signatures, and the other runtime DLLs packaged with PM are cut from the same cloth and work normally.
  11. Delete api-ms-win-core-memory-l1-1-0.dll from the Pale Moon folder and then it will run, falling back to Vista-compatible binaries in system32 installed by the VC++ 2015-19 runtime. This is the second program broken by Windows 10-derived runtime libraries (Code::Blocks was the first). Though in this case, there are no missing functions, but apparently that DLL delay-loads some functions that are certainly valid, but have ".dll" attached to them, making them invalid.
  12. There was an addition to the firewall API that allows newer versions of simplewall to run. But it turns out many of the other functions in the file are outdated which made it not function properly so no release for that yet. I also made modified versions of dbghelp/dbgcore which can be used for newer applications like Code::Blocks that need them in their program folders. And then there's still the issue of ntoskrnl blocking modified ntdll and win32k. I seem to have detected the functions responsible for the checks of the image hashes (which will also be good for 7, 8.x and possibly even 1
  13. Device Manager indicates that he used the MPS Multiprocessor HAL, which doesn't use ACPI. I just tried that HAL on X58 (which also works fine with ACPI) and confirmed that it does kill hyperthreading, along with Enhanced Intel SpeedStep.
  14. I see the first thing happening whenever windows are opened. Not sure why that happens since explorer is x64 and everything running under it should be. Which version of Kaspersky would that be?
  • Create New...