Leaderboard

I figured I'd make a group on Telegram, to perhaps get a few people that don't like/ prefer not to use discord. The group serves the same basic purpose as the Discord Server, a way for MSFN members to join and talk about MSFN and related stuff. The link to join is: https://t.me/msfnorg

Direct links to official Adobe Flash Player distribution packages version 32.0.0.293 with SHA-1 signature released today (should work with Windows XP SP3/Windows XP x64 SP2) Internet Explorer ActiveX: http://fpdownload.adobe.com/get/flashplayer/pdc/32.0.0.293/install_flash_player_ax.exe Mozilla Firefox NPAPI (also for Opera Presto/Google Chrome 44 and earlier): http://fpdownload.adobe.com/get/flashplayer/pdc/32.0.0.293/install_flash_player.exe Google Chrome 45 through 49 PPAPI: http://fpdownload.adobe.com/get/flashplayer/pdc/32.0.0.293/install_flash_player_ppapi.exe

Because they decided to. Same reason that anyone uses any program. but I booted my one 7 system with the MSE on it, let it update, no EOL nag there yet, FWIW

When I tried out FF 53, I discovered that some of my add-ons got disabled. The problem was with "unsigned" add-ons. Usually these were legacy add-ons that continued to be maintained after Mozilla banned pre-WebEx add-ons, and thus could no longer get Mozilla to sign them. The biggest example was the legacy version of uBlock Origin, which I use because it offers more privacy protections than the WebEx version does on FF 52 and 53. (A couple were add-ons that were originally signed, but from which I had removed the signature in order to implement some hack.) In FF 52 ESR, unsigned add-ons aren't much of a problem. You simply set the about:config preference xpinstall.signatures.required to false and you're good to go. The unsigned add-ons will produce warnings in the about:addons page, but they work. You can even hide the warnings with an add-on like Classic Theme Restorer. But FF 53 is a "stable" release, and xpinstall.signatures.required doesn't work in stable FF releases. Luckily, there is a workaround, but it's a bit more complex than just setting a preference. The workaround at the link can be combined with @VistaLover's fix for re-enabling SSUAOs in Firefox 52: First, follow the instructions there; then add this JavaScript to the config.js file you just created: try { Components.utils.import("resource://gre/modules/addons/XPIProvider.jsm", {}) .eval("SIGNED_TYPES.clear()"); } catch(ex) {} (I put it after @VistaLover's code, but it will probably work before it too.) One last thing. Since FF 53 doesn't expect to have add-on signing disabled, it doesn't have the yellow "warning" text that FF 52 ESR does for an "unverified" add-on. Instead, you'll see a scarier, red "This has been disabled" message. However, it has not been disabled; you'll still see a "disable" button which wouldn't be there if the add-on were already disabled. Luckily, hiding warnings (with, e.g., the Classic Theme Restorer add-on) will hide these scarier messages just as it hides the yellow warnings in FF 52 ESR.

Wondering the same. Symbols download fine, but I am still getting the DWM compatibility error. I have deleted and downloaded new symbols about 4 times and it does not change anything. If I click "cancel" instead of "retry" then Aeroglass works on 1909, but I have to do that every time do a logon.

I don't understand what you want. If you don't want them to move, then don't move them. Just because they "CAN" be moved to a new location, doesn't mean they will or can move by themselves. Or do I not understand the problem? Cheers and Regards

@VistaLover, it turns out it was because I was at 100% zoom on my 1024x768 screen. It does appear when I zoom out a bit.

I guess it's again time for the monthly batch of updates. KB4526478 - Servicing Stack Update for Windows Server 2008 - 32-bit | 64-bit KB4525106 - Cumulative Security Update for Internet Explorer 9 - 32-bit | 64-bit KB4525234 - Security Monthly Quality Rollup for Windows Server 2008 - 32-bit | 64-bit KB4525239 - Security Only Quality Update for Windows Server 2008 - 32-bit | 64-bit Optional updates: KB4528081 - Update for Windows Server 2008 - 64-bit (apparently this update lets Server 2008 machines get updates after Jan. 2020 but it's only available in the 64-bit flavor for some reason) And that's it for November updates for now, but I'm pretty sure another timezone update will be released in a couple days so will try to add it to this list as soon as it's out.

The actual AOL website notes that the chrome version of shield has NO XP/Vista compatibility

This happened to me too. If I remember correctly, what it ended up doing was adding the contribution amount to my existing login. So instead of $5 total donated it shows up as $10 kind of thing. I think this worked out better, because the number of licenses was more for $10 than it was for 2 x $5.

Then if AeroGlass needs only a whitelist string please BigMuscle give us customers a small update-release!

Bitte nicht auf Deutsch posten! Nur Englisch ist erlaubt hier.