TSNH

I'm getting this "help protect..." on the mobile j2me youtube client Jtube which uses invidious (remote) proxy, and with TorBrowser "Sign in to confirm you’re not a bot" but not on JDownloader with my local ip

Were you using Windows 7 without DWM? (Windows 7 basic, Classic or high contrast theme). If so then Windows 10 doesn't support running without DWM, but I'm sure these guys https://winclassic.boards.net/ tried making it work (I haven't read into details). Dark theme implementation in Windows 10 and 11 is still far behind what could be achieved with custom themes and classic theme, it doesn't recolor the UI automatically like those custom and classic themes did, but every single app must support it. There are still many apps in Windows that don't.

Folder background color is controlled by themes not registry. High-contrast themes can have non-white background. They don't look that well, but use may look for custom themes based on them

Here are registry files that apply Windows 8.1 Metro/UWP coloring styles that exactly match those known from beta versions of Windows, they cannot be achieved by changing personalization options in settings. This changes both colors for the current users and when no user is logged in. Save chosen one as .reg and apply: Windows 8 Developer Preview green Windows Registry Editor Version 5.00 [HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Explorer\Accent] "DefaultStartColor"=dword:ff386d0e "DefaultAccentColor"=dword:ff51a110 [HKEY_CURRENT_USER\SOFTWARE\Microsoft\Windows\CurrentVersion\Explorer\Accent] "StartColor"=dword:ff386d0e "AccentColor"=dword:ff51a110 Windows 8 Consumer Preview teal Windows Registry Editor Version 5.00 [HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Explorer\Accent] "DefaultStartColor"=dword:ff504000 "DefaultAccentColor"=dword:ff878200 [HKEY_CURRENT_USER\SOFTWARE\Microsoft\Windows\CurrentVersion\Explorer\Accent] "StartColor"=dword:ff504000 "AccentColor"=dword:ff878200 Windows 10 Technical Preview blue Windows Registry Editor Version 5.00 [HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Explorer\Accent] "DefaultStartColor"=dword:ff6d4a30 "DefaultAccentColor"=dword:ff8a6e59 [HKEY_CURRENT_USER\SOFTWARE\Microsoft\Windows\CurrentVersion\Explorer\Accent] "StartColor"=dword:ff6d4a30 "AccentColor"=dword:ff8a6e59 Note that the color format is ff meaning opacity and than BBGGRR so kind of reverse (you can set any color you want) Does not work on Windows 8.0 (although Consumer Preview teal can be set in standard preferences idk about others)

https://msfn.org/board/topic/183046-guide-vista-extended-kernel-installation You can copy x64 files manually or replace extended files in syswow64 with original ones after using the installer. I never install 32-bit files because they break some programs that work in vanilla while x64 ones never do. (x64 java control panel is an x64 application, so it shouldn't be affected, but idk),

Does work fine for me with x64 jre-8u181 on Windows Vista ExK October 2022 with only x64 extended kernel files installed (the control panel for x64 java is an x64 application)

You don't need experience index to complete to get Aero Glass, just install video drivers and enable Aero theme in personalization options

Yeah, maybe the mods @Tripredacus@Dave-H or others could tell (assuming they are allowed to share this information) if there was some unusual activity on @viixiduu's account (maybe it was hacked and then deleted) or he just removed it.

@Vxiiduu's MSFN account has been removed too! https://msfn.org/board/topic/182001-porting-snipping-tool-to-windows-7-from-windows-10/?do=findComment&comment=1210733 Do MSFN moderators have any information on what exactly happened?

Reserved

AMD Raven Ridge Ryzen modified iGPU driver for Windows Vista My modified driver inf for AMD Raven Ridge Platform is ready to be released and here it is! It supports Radeon Vega mobile graphics integrated with Ryzen 3 2300U, Ryzen 5 2500U, Ryzen 5 2700U. The driver inf file is my modified version based on a 21 december 2017 Windows 10 Acer OEM driver inf, but is used here to install a much newer Win10 driver from early 2018 with patches and fixes till 8 march 2019. Feature set: https://msfn.org/board/topic/186330-windows-vista-on-amd-ryzen-mobile-raven-ridge-vega-graphics-testing/?do=findComment&comment=1269617 Download: https://forum.legacydev.org/viewtopic.php?f=27&t=218 Installation process: Preparing drivers Install CFF Explorer and 7-zip Download the 2017 driver: https://www.catalog.update.microsoft.com/Search.aspx?q=22.19.655.5888 Rename the downloaded .cab to "2017.cab" Download the 2019 driver: https://www.catalog.update.microsoft.com/Search.aspx?q=23.20.826.9472 Rename the downloaded .cab to "2019.cab" Extract both with 7-zip to their respective folders called 2017 and 2019 Go to 2019\B340050 directory and locate all .sys files there. For all 3 files, open them in CFF Explorer, go to Import Directory and rename ntoskrnl.exe to ntoskrn8.sys. Then go to Rebuilder and untick Rebuild PE Header and tick Update Checksum, click Rebuild, than save. In 2019\B340050 folder rename coinst_17.40.dll to coinst_17.30.dll Go to 2017\B322218 and copy all files from there that are missing from 2019\B340050 to 2019\B340050 i.e copy all files from 2017\B322218 to 2019\B340050 but WITHOUT replacing. Clear 2019 folder from all files (inf and cat) that are not in 2019\B340050 folder. Download modified .inf file (if you haven't already) Put the modified file in the 2019 folder Driver should be ready, now let's move to preparing your system. Preparing your system Install x64 October 2022 Extended Kernel if you haven't already https://forum.legacydev.org/viewtopic.php?f=27&t=209 Download and compile George King's modified NTOSKRNL_EMU Extender https://msfn.org/board/topic/184042-amd-radeon-graphics-driverdriver-pack-for-windows-vista/?do=findComment&comment=1227975 https://board.eclipse.cx/viewtopic.php?t=404 https://github.com/GeorgeK1ng/NTOSKRNL_Emu Put the compiled ntoskrn8.sys into your %windir%\System32\drivers directory https://board.eclipse.cx/viewtopic.php?t=404 Open start menu, search for msconfig.exe and open it Go to boot tab and tick "No GUI Boot" checkbox, than click ok to save changes Installing drivers Install driver from 2019 folder using the device manager, confirm installing unsigned driver Don't restart when prompted yet Go to %windir%\System32 and rename atiumd6a.dll to atiumd6a.dll.backup Go to %windir%\SysWOW64 and rename atiumdva.dll to atiumdva.dll.backup Congratulations! Restart the PC, drivers should work on restart Known Issues Driver may hang on system bootup (hangs on around 1/5 of bootups). Not sure whether this is related to Ryzen Vista issues or the driver, likely not fixable with .inf edits. You may hear funny repeated startup sound chord when it does hang. After booting the OS is 100% stable from my testing, no gaming tests though. Feature set is limited, see feature set above Entering sleep mode takes around a minute Note that Ryzen platform can have BSOD issues completely unrelated to the display driver, read https://msfn.org/board/topic/186330-windows-vista-on-amd-ryzen-mobile-raven-ridge-vega-graphics-testing/ and think twice before buying Ryzen products just for Vista. But anyway if someone figures out how to solve all BSOD issues the driver is already there. Special thanks to: @win32 for the Extended Kernel @K4sum1 for Guide to getting AMD 17.10.1 drivers working on Vista @Cannonkong for MessageNumberLimit fix @George King for adding necessary features to NTOSKRNL_EMU Extender

I got a driver from 8 march 2019 working. https://www.catalog.update.microsoft.com/Search.aspx?q=23.20.826.9472 It is actually a driver with from early 2018, but patched with fixes till 2019, so all the issues of the driver being just bad should be resolved. I actually still sometimes fails to load on startup and hangs, but I don't think this can be resolved in the inf file or if it's actually driver's fault and not running on Ryzen (this hang is not a BSOD but idk). The performance is better that with the old driver. After the startup the driver is 100% stable with feature set described in one of my previous posts. To install it I'm using modified version of this Acer OEM inf from the previous post so it's not based on @Cannoncong's inf except for one fix that he figured out: I'm going to release the modified driver soon as I don't think anything else can be improved without modifying the .sys files.

Lately I've been testing Windows Vita on AMD Ryzen mobile platform. https://msfn.org/board/topic/186330-windows-vista-on-amd-ryzen-mobile-raven-ridge-vega-graphics-testing/#comment-1269685 The OS is stable once it has booted so it's mostly usable, but this cannot be said about virtual machines running on this hardware. The stability is WAY worse there. It seems that Ryzen issues affect virtual machines running using AMD's virtualization technology way more that the host. Guest machines (Windows 11 and Linux) would randomly hang, endlessly display what was on the screen just before the crash and cause 100% CPU usage on cores that were assigned to the virtual machine. It doesn't harm the host OS, you can just run taskmgr.exe and close the affected virtual machine This makes me think Ryzen issues lie deeper than in the USB controller, CD ROM drivers and the likes. It may be related to no drift correction as on Haswell, I guess Windows build 6519 would have to be tested to know for sure. So far ppl have reported different builds to be the ones that fix the Ryzen BSODs https://board.eclipse.cx/viewtopic.php?p=2910#p2910

The original SHA-2 hash for KexSetup_Release_1_1_1_1375.exe is 652f6d2901c86de4a05743b5f808fafb6e28b9720c39bce5e7e031d26cac9035 And it matches with re uploads from commandcontrolQ and VxKex/VxKex commandcontrolQ stated that: The VxKex/VxKex one looks suspicious tho as it looks like it's baiting for donations in Bitcoin (which wasn't the case with the original release) and Readme is also heavily trimmed. If @vxiiduu re released the official version, they would have probably let us know here.

Actually some of the driver instabilities are not Vista - specific and occur just because those early drivers were really buggy even on Wndows 10 https://community.amd.com/t5/drivers-software/crashing-video-driver-ryzen-5-2500u-vega-8-hp-x360-laptop/td-p/294858 So now I'm using this Acer OEM (not HP) driver as it's more stable. https://www.catalog.update.microsoft.com/Search.aspx?q=22.19.655.5888 It it a slightly newer version and doesn't feature JPEG acceleration which may have been causing issues on the HP one. So now the driver is stable after it has been loaded, but can still crash on boot and shutdown

Certain AMD video drivers can make BSODs appear corrupted or as plain black screen which can make it hard to distinguish them from regular display driver hangs or (integrated)monitor connectivity issues. To diagnose issues correctly it's a good idea to enable MiniDump and disable automatic restart on system failure: Go to sysdm.cpl (search for it in the start menu) than advanced tab, startup and recovery settings, select small memory dump and disable "Automatically restart" checkbox BSODs Block all input devices and sound Do allow for system shutdown with a single short power button press. Can generate a MiniDump in %SystemRoot%\Minidump. MiniDump may not get generated if you shutdown too soon and don't let a BSOD "run" for some time (1 minute should be safe) or saving data to disk has failed. To read minidumps you can use BlueScreenView from nirsoft Display Driver Hang / Black screen Usually block all input devices and sound Do NOT allow for system shutdown with a single short power button press. You have to hold it to shutdown Don't generate a minidump, you may want to search the eventlog (integrated)Display connectivity issues Input devices and sound works as system continues to function.

It doesn't support dx12, When you hover over that textbox it explains that it ts only about whether the GPU's hardware supports dx12 (probably takes this info from some list) and it doesn't test whether drivers and OS also do. As for what works on this driver: dx9 - works dx10 - not tested, but should work like dx11 dx11 - works as browser HW acceleration, but not in games. Vulkan - doesn't work (I made no attempts at fixing it or using VulcanRT installer but it's very low priority thing on this laptop) OpenGL - not tested yet Video decoder DXVA - Doesn't work and causes a BSOD when you attempt to use it. Had to remove atiumd6a.dll from system32 and atiumdva.dll from syswow64, so that video playback just falls back to software rendering OpenCL - doesn't work

I solved this issue! All you have to do is enable non-GUI boot in msconfig. I don't know why this makes any difference but it does.

Latest versions of Chrome and Firefox are not compatible with Vista ExK and 7 anymore, Supermium and r3dfox are modified versions of those 2 browsers respectively that work on Vista and 7, so you should try those instead

It worked! I putted it in sleep mode, it looks like Windows does successfully enter sleep mode, but the hardware does not (fans were still on in this "sleep mode"), resuming took around 30 seconds (probably waiting for some timeout), not sure how reproducible this is UPDATE: It is definitely reproducible, (I'm writing this post update from my Ryzen laptop on Vista). The computer does in fact go into sleep it just takes 30-60 seconds again probably there is some minor error and it's probably waiting for some timeout of a minor feature that doesn't work The driver is not very stable however, after around 15 minutes I got a BSOD of dxgkrnl.sys and ks.sys, likely caused by the driver. Bluescreens are not visible, the screen turns black I'm reading this off MiniDump. About this screenshot: GPU-Z says this is 17.10.1 which corresponds to Windows 7 drivers that I took some files from as replacement for their Windows 10 HP OEM equivalents. The OEM driver alone is identified by GPU-Z as 17.7. Later it turned out that it makes absolutely no difference to the driver's functionality on Vista, so I may as well stay with Windows 10 files.

I've decided to try out Windows Vista on AMD Ryzen 5 2500U, the Raven Ridge mobile platform. First drivers for their integrated GPU (OEM ones for Windows 10, not straight from AMD) predate 17.10.1 drivers which can be made to work on Vista: https://board.eclipse.cx/viewtopic.php?t=404 I've installed the OS (with Extended Kernel) on a VM and then applied vmdk virtual disk image onto a M.2 SATA SSD which was then installed in the laptop, and booted from it in Legacy/CSM mode Initially there were some BSODs, but they stopped occuring after I removed optical disk CD drivers from 'c:\Windows\system32\drivers' cdrom.sys and cdfs.sys. If you remember they where one of the causes of BSODs on Ryzen systems. The other one was of course USB controller, but it's clearly not causing issues here, bluescreens were significantly less frequent from the start than on my old Ryzen desktop and after removing those CD drivers stopped occurring completely and the system is fully stable now. Even USB 3 works with @cannonkong's modified drivers https://winraid.level1techs.com/t/solution-win-7-win8-1-x64-ryzen-apu-video-driver/34203?page=1 The only thing that doesn't work yet is the GPU. Is is officially only compatible with Windows 10 Redstone 1607+, but @cannonkong managed to get is working on Windows 7, 8.1 and 10 Threshold (1507 and 1511) with just an .inf mod. The oldest version of his modded drivers of from 2019 unfortunately so I tried applying simmilar patches to this HP OEM driver from 09.2017 https://www.catalog.update.microsoft.com/ScopedViewInline.aspx?updateid=808a5b95-4eb0-4be6-82f6-58fad73c2708 I succeeded for Windows 10 Threshold 1511, but on Windows 7 this driver launches successfully, but you can only see distorted image and then nothing on the screen. Despite that that system works, you can change backlight brightness click on things and hear sounds. This issue can be however completely fixed by going into sleep mode and resuming. The GPU works ok after that. On Vista the symptoms are the same as on 7, but sleep mode doesn't work, so you can't use this as a workaround. You can even see Aero working for a moment, and than black screen (you can still hear sounds and interact with the OS). So a simple tweak could make it work. Do you have any ideas? EDIT: I've tested system's stability without GPU drivers installed and it survived all 7 hours of testing, which included 2h of video playback (on Microsoft Basic VGA adapter) and also around 2h of web browsing, it hadn't crashed a single time. However when I started messing with GPU drivers, a BSOD caused by video drivers would often be followed by another one in a very early boot stage including when entering SafeMode, so I'm not sure anymore. Perhaps the potential for Ryzen-like BSODs exists, but after removing CD drivers nothing is using system resources in a way that causes BOSDs

Anyone tested this with an old version of WebView2 like 109 https://www.catalog.update.microsoft.com/Search.aspx?q=webview2 Runtime version 109 on Vista/7/8/8.1 ?

32-bit version https://msfn.org/board/topic/173175-catalyst-1412-omega-on-vista/ This says 14.12, but also works for 15.6 You should have been able to install drivers with just the .inf file mod (replacing 6.1 section's name with 6.0), this patch solves just powerprof.dll error.

I think that they are making a big mistake with Wayland, just because it is not X11 with improvements . One of the main reason why Windows is still so popular is that almost nothing gets removed from the api, you can still run most Windows 95 desktop apps on Windows 11. Corporations and developers of other software value backwards compatibility a lot. You can't expect everyone to update their software just because you now consider a feature they relied on obsolete (having everything running in xwayland is also not a solution). Developers (especially hobbyist) tend to flag something as obsolete as soon as they come up with a better idea before even implementing it in a stable way, there is just no corporation to remind them of all the customers they may lose in the process.

Should work with 15.6 AMD Catalyst drivers https://forum.legacydev.org/viewtopic.php?f=27&t=199