Jump to content
Strawberry Orange Banana Lime Leaf Slate Sky Blueberry Grape Watermelon Chocolate Marble
Strawberry Orange Banana Lime Leaf Slate Sky Blueberry Grape Watermelon Chocolate Marble

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. Alternatively, register and become a site sponsor/subscriber and ads will be disabled automatically. 


  • Content count

  • Donations

  • Joined

  • Last visited

Community Reputation

95 Excellent

1 Follower

About UCyborg

Profile Information

  • OS
    Windows 8.1 x64
  • Country

Recent Profile Visitors

1,887 profile views
  1. UxTheme Signature Bypass

    I ended up patching system files with that method as well. No dependency on AppInit_DLLs and secure boot status, no random blue screens or cancelled logins that may arise when using Aero Glass's CreateRemoteThread method, no issues with .deskthemepack files, works when applying themes via Windows 10's Settings app and the chosen them loads even in Safe Mode. Interestingly, with original files, system just falls back to default theme in Safe Mode rather than freaking out. Also ran the patcher on 32-bit system to get patched versions of 32-bit files, for consistency.
  2. Official - Windows 10 Worst Crap Ever!

    My Win10 Build 16299 install is still going. No apparent data corruption despite the strange errors in Event Log. Windows Update history almost fully clean with one failed Flash Player update which got installed successfully the second time around. How did hibernation file get a size of less than half the RAM amount without touching powercfg remains a mystery, but it sticks after correcting the setting. Found another inconsistency. Using USB tethering to access the internet via Android smartphone and setting *NdisDeviceType to 1 in registry to stop the system from creating and asking for a new network location every time it's plugged in makes the notification area network icon indicate no internet connectivity. Clicking on it does show the Connected status for the device and so does the network indicator on the login screen. UWP apps behave as if there's no internet so can't check for updates. Internet Explorer browses the web just fine. Still getting a bit stuttering graphics with NVIDIA's Windows 10 graphics drivers. The issue goes away with older ones predating Windows 10. Newer drivers for older systems refuse to work on Windows 10. It seems they've made software compositing via WARP slower. Got smooth window animations on Windows 8.1 in safe mode, but they're choppy on Windows 10. And the big UWP app opens after logging in and tells you you're not connected to the internet. Did they forget to make safe mode with networking mandatory? Regarding the Settings app; I don't know if things are better in 2018 when it comes to stability. Back in 2017, it would almost always crash on me when going through the settings A - Z, somewhere in Privacy section. They've also changed auto accent colorization change to quick and abrupt from smoother variant (eg. when the desktop background changes). The background change is still animated and the AnimationDuration setting in registry respected. Maybe the swift accent color transition is meant as an optimization? Smoother version does spam application windows with more WM_DWMCOLORIZATIONCOLORCHANGED messages, but looks nicer. Now what rough edges may the RS4 bring?
  3. WHEA hardware error ?

    The WHEA event you showed is just normal WHEA subsystem initialization event. AFAIK, the reported errors appear at Windows Logs->System with WHEA-Logger as the source. An example: Been getting this one for years on each boot, the system still operates reliably. WHEA only catches certain errors. While not everything is at 100% as it should be, the uncorrected error would be probably more critical. You may want to test RAM with Memtest86, maybe try a different graphics card or test your current one on another machine, if possible. Sometimes motherboards break in strange ways. There's a number of possibilities, those are just quick guesses.
  4. Aero Glass GUI

    Good point, setting it to 0 takes the ability to change the other setting.
  5. ...and you've gone through the usual tricks of checking if some application or driver is blocking these actions, it's possible that Windows allocated itself a hibernation file that's not large enough. This could be the reason if classic non-hybrid sleep and shutdown work properly. Try this command from administrative Command Prompt: powercfg /H /SIZE 100 This sets the hiberfile.sys size to maximum size, which is is the amount of installed RAM. The default size didn't work on my PC with 4GB of RAM for some reason since the FCU, though the issue never occurred with more memory starved machines at my house. You can also play with TYPE setting, the documentation's on MSDN. If the issue goes away after restart, then that was it. I hope it helps someone.
  6. Vulkan Backport On Vista

    OpenGL 4.6 was released about a year after 372.70 drivers, so support for it is non-existent in older drivers.
  7. Launching latest iTunes.exe pops up a message about missing K32GetModuleFileNameExW. For Private Internet Access VPN, my guess is that it uses different API for version check. There's also some pia_nw.exe in the package that refuses to launch due to missing PowerClearRequest. I think version check bypass only works for those applications where their devs kept it simple and only excluded Vista due to its bad reputation and to not get support requests from Vista users. The system requirements are outdated, that's on Windows 7+.
  8. Aero Glass GUI

    The same setting that worked in previous Windows versions is ineffective on Win10. Another setting also affects some other parts and doesn't make a difference when you try to make caption text white. I can only suggest a workaround. Try different accent colors in Settings app->Personalization->Colors until you find the one that has the side effect of making caption text white. The exact issue is that Win10 uses 2 colors for caption text, black or white, depending on current accent color. White can be replaced, but I haven't found a way to override the black.
  9. Vulkan Backport On Vista

    That's just a loader. The actual parts responsible for rendering are implemented in the same driver DLL as OpenGL on NVIDIA's side, which is named nvoglnt.dll on XP and nvoglv32.dll/nvoglv64.dll on Vista+. Nothing is reported on XP by vulkaninfo besides the presence of 3 basic instance extensions. Normally, you get tons of info about GPU capabilities.
  10. Vulkan Backport On Vista

    For all practical purposes, Vulkan support in XP is non-existent. NVIDIA driver version 364.51 only has stub functions for vulkaninfo to not report any errors, but no actual functionality to render stuff is implemented. The stubs have been removed from later drivers. The Vulkan runtime is not the problem, official runtime runs on Vista. The initialization fails from the driver side. It needs some Windows 7+ specific D3DKMT functions.
  11. Wolfenstein: The Old Blood Creative Sound Blaster X-Fi MB3 This is another case that officially supports only Windows 7+, even though the software works on Vista without issues. The only obstacle is the installer that refuses to proceed beyond welcome page unless it detects newer OS. I used OllyDbg to attach to the installer process, set a breakpoint on GetVersionExW function and modified it to return version 6.1 in dwMajorVersion and dwMinorVersion members of OSVERSIONEX structure. Setting memory breakpoint on dwMinorVersion member helps to pinpoint the memory where the value is copied from. Two other programs: Actual Window Manager - the oldest OS still supported is Windows 2000. DisplayFusion - the support for XP and Vista was dropped at one point. The link to the XP and Vista compatible version is provided on its website. Also must have a KB2763674 hotfix installed.
  12. Aero Glass GUI

    It was is smaller on Windows 7 too with Aero and Basic themes when maximized. Win10 adds the additional scaling of title bar buttons. Set border padding to zero with Winaero Tweaker for the smallest difference between the height of normal and maximized window's title bar.
  13. Server 2012 Updates on Windows 8

    Mitigation for Spectre Variant 2 was reported to have the noticeable performance impact for the things that need to frequently callback into the kernel; networking and I/O operations. This one also needs CPU microcode update, which it seems most hardware out there won't receive it. A DLL cannot load by itself. It relies on ancient AppInit_DLLs functionality from the NT4 days. It would be stupid to keep it around, for the fact that it doesn't work with secure boot alone. And the current experimental version for Windows 10 happens to be the first version in years with virtually zero visual glitches.
  14. Aero Glass GUI

    Regarding inactive caption font color, I think it's preset to dark gray. Would be nice if it could be changed. On Windows 8.1, this can be easily achieved by modifying the right properties in .mssytles file, both for active and inactive windows, so AG is not needed for that, just a custom theme. I'm unable get any consistent results on Windows 10. The system always mixes the chosen inactive color with the gray color. And whether the chosen active caption color in .msstyles file is in effect depends on selected accent color. Unlike Windows 8.1, Windows 10 uses 2 separate colors (black or white) for active caption font, depending on the selected accent color, probably to improve readability so you get brighter font on a darker background instead of both being dark for example. So you'd have to find the way to override both default colors, not just one. AG probably could have an option for changing inactive caption color, though you'd still be stuck with defaults for windows with their own caption font rendering.
  15. Interestingly, with the current stable version of AG, only the colors specified in the "Glass colors" are used for all parts around the window while the latest experimental version, the ones on "Accent" tab are also taken into consideration to give the sides and bottom of the window a different color. The rules change for the windows of ribboned Explorer, Wordpad, Paint etc. where inactive color from the Accent color is used for all parts as seen on your screenshot. I remember it used to be like it is now with the current experimental older stable versions, though I haven't messed with those colors in months so I haven't noticed until now. Without AG, it appears the color of side and bottom parts of the inactive window frame cannot be changed. That shouldn't happen. Only at logon and not also at closing and reopening GUI? Haven't noticed anything off with that, but I've discovered another bizarre problem that occurs with the combination of debug version of AG and Classic Shell. If I click in the debug console to activate select mode and then click anywhere on the taskbar, screen freezes. I can only initiate graceful shutdown with a press of a power button. If I do this in a virtual machine, I see the process hosting it hogging one of the CPU cores at 100%. I tried remoting into a virtual machine while it was hung, I was able to login with a different account and the process hogging the CPU is dwm.exe. Well, it makes sense since it's responsible for drawing on the screen. There are references to DWMGlass.dll in the stack trace of the hanging thread shown by Process Hacker. if you login with Classic Shell disabled, click on the console, start Classic Shell, then it also hangs. It's not necessary to click the taskbar in the first scenario, just pressing Win key also does it. Or alt-tabbing. It seems anything involving the taskbar triggers it. Fortunately, it doesn't seem to happen with any other console window or without Classic Shell, but I still think it's strange.