TSNH

It is available if you install Windows 7 AIK, it is officially supported by Microsoft Someone in the MDL thread I linked recommended a newer Chinese modified DISM by Chuyu-Team for Vista (you have to login to view their post), but idk about that

It has been a long time ago since I last did that (now I have an ISO with integrated updates), and I didn't post a link, because back then I just deleted (running 7-zip file manager as Trutedinstaller) all amd64.something and x86.somenthing folders with the date modified matching what I wanted to delete. But while effective, that's not a proper way, as it may break your Turn Features on or off and possibly other things, Perhaps look at this: https://forums.mydigitallife.net/threads/how-to-peform-a-full-winsxs-cleanup-for-vista-and-windows-7-series.87379/

If you install KB4493730, than do restart to make sure it's installed than KB4474419, it should just install. First of all I would revert to a system restore point before installing updates that broke, because this reverting thing could have created a mess. Did you install all the earlier updates till 2017, If so: Quick search for this "Updates were not configured currently" shows that it can be caused by installing too many updates at once, so when installing updates try installing like 10 and than restart. If not, well, maybe those 2009-2017 updates and they are worth installing

The SHA-2 update (2019) updates most critical kernel files but doesn't update "all" files, so if you don't install other updates some of them may stay on let's say 2010 version insted of 2016. Is it a problem? It shouldn't be, but sometimes some system files expect files that they interact with to be in a fairly close version and they don't run well with too old ones. I remember I've ran into this issue once with Windows 7 To help cleaning the mess after installing updates read about cleaning up WinSxS

You can try looking for laptops with CPUs with NO integrated graphics (yes they do exist (i mean for sure 9300HF exists :) )) https://www.notebookcheck.net/Intel-Core-i5-9300HF-Processor-Benchmarks-and-Specs.462517.0.html And those can't possibly be running with Optimus. Weird AMD CPU + Nvidia combos like the one @Aiek link also look promising, but I'm not sure AMD + Nvidia immediately means that they are fine. But beware that those new Lenovo Legions with Intel 9300HF (and maybe AMD too) have touchpads restricted in ACPI to Windows 10+ and they don't even show up in device manager in Windows 8.1 and below https://msfn.org/board/topic/184465-intel-hid-event-filter-driver-with-modded-acpi-windows-7/

6002 is actually Vista service pack 2, 6001 would be sp1, and 6000 the original release. Officially however you need also all Vista updates till 2017 not just sp2. Some users reported success with only installing some updates (you need platform update and supplement for sure, but there are also others needed), but here are all of them, (you don't need hotfixes unless you are specifically affected by issues they fix and you also probably don't need Media Center TV pack etc.) https://msfn.org/board/topic/181756-windows-vista-update-repository-until-april-2017/?do=findComment&comment=1185620 You may need to get used to the bulk installations with scripts described there you are probably missing some updates

Actually also still works on Windows 2000 BWC ExK

Are you sure you ran bcdedit /set {current} nointegritychecks yes ? Here is how to do this post installation, but it's a bit harder that pre-installation https://msfn.org/board/topic/183046-guide-vista-extended-kernel-installation/?do=findComment&comment=1246958

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