Leaderboard

Signed up here principally just to thank heinoganda for his MSE Updater tool. I'm using Window 7 Pro 64 with its XPMode 32bit running on a VM (Virtual Machine) and I installed MSE on that XP VM as an ideal fit for this sort of purpose. Automatic definitions updates and manual updates via MSE stopped working in 2016 but I've been happy enough to download the MSE AV definitions update mpam-fe.exe on a weekly basis and install it that way. I've been doing that mostly without problem for three years. But then this new install problem suddenly happened and over the last month I've had very little luck even finding out that it was a typically MS way of ending support for something. Not providing any particular warnings let alone reasons why it is going to happen. Just doing it and letting the user sort it out themselves. I was pointed here by a helpful guy on another PC forum where I'd posted about the problem and I'm very grateful to them for doing that. I can confirm that the v1.9 MSE Updater works on my system (as described). My MSE installation is now showing it is up to date with the latest definitions. Thank you.

@WalksInSilence Thanks for the nice words and welcome to MSFN! I am pleased that the MSE Definition Updater Version 1.9 does its work for you.

Welcome to MSFN!

Microsoft will have "dropped" Win7 in mid-January 2020, so, of course, they would find no justification for a new .NET FW release, 10 months after Win7's EoS, to have backwards compatibility with OSes they wouldn't service at that time ... I'm just lazy to check, but I suspect .NET FW 5.0 to require Win8.1+...

Update for root certificates: New: CN = Trustwave Global Certification Authority O = Trustwave Holdings, Inc. L = Chicago S = Illinois C = US CN = Trustwave Global ECC P256 Certification Authority O = Trustwave Holdings, Inc. L = Chicago S = Illinois C = US CN = Trustwave Global ECC P384 Certification Authority O = Trustwave Holdings, Inc. L = Chicago S = Illinois C = US CN = VRK Gov. Root CA - G2 OU = Varmennepalvelut OU = Certification Authority Services O = Vaestorekisterikeskus CA C = FI Those using heinoganda's Cert_Updater.exe should run it ASAP. Others needing a redistributable rootsupd.exe should follow his instructions for creating their own, or PM at 5eraph for an updated EXE file.

Now a lot of different hardware variants are in use by the users, nice if the one variant works on both of your computers, but what about the other users? Do not have to make because of a user (you) again a huge effort. You ought to have read the following two sentences from one of my previous comments: Maybe this explanation is enough for you!

Speaking of .NET Framework, Microsoft is gonna release the new .NET Framework 5.0 on November 2020. They can't wait to drop Windows 7 and do to it what they have done to XP, I guess...

Apparently my assumptions were incorrect, and so is this thread's title. I searched through Chromium's commit history and found out only the option in chrome://flags was removed, the functionality is still intact and can be invoked using a command line parameter, see here. So one must add --disable-features=Windows10CustomTitlebar parameter to Chrome's shortcut properties, at the end of the Target field on the Shortcut tab. This method doesn't have any undesired side effects like running in compatibility mode has.