FranceBB

Yep! Thank you, for those updates! I mean, I'm probably never gonna use them anyway, but it's nice to have XP updated.

Does it have the added nag as well? (I'm talking about the white box meant for ads popping up on the bottom right corner).

Ok. Updated once again.

+1 for Anydesk. I've been using it for 2 years now (ever since Team Viewer began behaving not-so-nicely on XP) and it's indeed a good replacement.

Yeah, same here... I noticed it as well and I didn't know what that was about... I really hope they're not gonna go on with it as I don't really think that's the way forward. Besides, it's using and redistributing open source projects and dlls, including FFMpeg, Avisynth and VapourSynth, Madshi (which uses MadVR) and many plugins for both frameserver, so I don't really think that inserting advertisement pleases the open source community. As one of the Avisynth contributors, I don't really like where PotPlayer is going...

Yeah, well, Norton? It's hardly gonna be missed... It couldn't catch a virus even if it hits its DLL xD

Fair enough, but I think Adobe should let users choose as there machines that are either offline or behind an intranet not directly connected to internet and by injecting a timebomb they'll make production machines stop working which is far more annoying and disrupting...

It's like an e^-0.3x: it's flattening, yet approaching zero...

Yep, that's indeed a VM with XP on it, which just shows that there are some programs that don't run on newer version of Windows and clearly don't run on Mac OSX.

Done. + Additional Topic Cleanup. Thank you for keeping ffms2 updated as well, by the way. You're a life saver for the whole Avisynth community.

Surfaces are made by Microsoft so I highly doubt that they made drivers for XP given that they're desperately trying to kill it in every possible way. By a quick search, it looks like the official page for drivers is: https://www.microsoft.com/en-us/download/details.aspx?id=57514 which apparently doesn't show XP as supported. Maybe you can look for drivers elsewhere and see whether they were released and then deleted by Microsoft or something like that, but given that the Surface 6 was released on October 2018, I'm not so sure M$ ever made drivers for XP... I'm sorry, I don't get it. If you're planning to use a VM instead of a physical installation, sure, you can install XP or other OS (provided that your CPU is x86 as architecture and not ARM).

Nice catch! So Microsoft is still releasing updates for the Premier Support and will do it after 2020?! O_O I thought the final deadline was July 2020 even for this kind of support, I didn't know that! Well, that's good news, it means that there are enough companies running XP so that it's still profitable for them to release updates past their original deadline (July 2020). Too bad he's anonymous... I would love to get my hands on those updates... If only Microsoft allowed private customers to buy them for a reasonable price... Yeah, sure: The fact that 0 patches were applied doesn't mean that it's not doing anything, it means that even when I opened patched programs like Java, Zoom, Adobe Acrobat Reader and so on, according to my usage, the patch didn't need to be injected directly in memory, as I probably didn't use a certain feature etc. The list of patches is huge, though: It actually updated itself automatically. It notified me that a new agent was released and it downloaded-installed-rebooted itself automatically.

Wow, thanks! I'm gonna install them right now!

Yeah, we've been using PotPlayer for years now and it's a very good player as it relies on Open Codecs which still support XP. As to unofficial LAV Filters build, there aren't any... at least not that I'm aware of...

Yeah, I've got the very same message as everyone else... I guess it's over, guys...

Actually there's: https://forum.doom9.org/showthread.php?t=175829 Which is why I told @Dibya to upload his new Audacity build there so that I could update the post (I didn't have to re-compile it myself this time since he did all the work), but he didn't reply... He's probably busy, but I'll tell him again: please, upload it there and I will add it to the main post.

Oops, I missed the updates... But still, I kept it running every now and then and it has been working fine 'till now, when I noticed that it failed to update the certs. Anyway, I updated to 1.6 which is your last version and now it's working fine again. Thank you

Well Better than nothing, I guess... Perhaps someone will come up with a registry "defuse" for the Adobe "time bomb" to use on the official installer...

That's bad... I mean, putting notifications, fair enough, introducing a banner saying that it will be discontinued, fair enough, but removing the whole archive and putting a time-bomb inside an executable?! I mean, c'mon... I know that they're doing it for security concerns, but honestly, they shouldn't take such an extreme measure, 'cause perhaps I'm not on a machine connected to internet, perhaps I wanna run .swf files locally... Adobe shouldn't artificially block Flash, it should be up to the users, really...

Yes, that's essentially what I have been doing with the normal Java files from here https://www.oracle.com/java/technologies/javase-jre8-downloads.html and it has been working so far, but I never modified the registry. I was lazy, so I simply began to extract the new version inside C:\Program Files\Java\jre1.8.0_144 so that it was going to detect the new version as the registry was pointing to that folder. What I don't like is that this way the folder jre1.8.0_144 has been storing anything but 152 'cause I kept extracting files in there ('till very recently when we also had to replace some files for the reasons I mentioned in other posts). Ideally, I'd like to manually store jre1.8.0_xxx where xxx is the correct name for that version and have it ok in the registry, which is why I hoped that the Azul installer was working. I mean, sure, I can just extract it in the C:\Program Files\Java\jre1.8.0_152 and replace sunmscapi.dll just like I've been doing for the other version of Java so far, but that's not the point. EDIT: Actually I downloaded and extracted it in the fake jre1.8.0_144 and it's working just fine by replacing sunmscapi.dll, as I supposed... Here you can clearly see that I kept every version of Java but then I had to stop and just fill _144 with whatever version was released... but inside there was 251 and now there's 262 of course...

I hope so, so they can report their experience and tell me whether it's only me and my system or not... On my XP x86, the installer does its job and the installation completes successfully. A new folder inside C:\Program Files\ is created called Zulu or something (I don't remember) and inside there's the classic Java folder structure with all the files, however, if I try to open a website to check which version gets reported, I don't get the new one, but the old one from the Java folder. If I try to replace the sunmscapi.dll to get it working and I test it again, nothing happens, it still reports the old version as it's pointing to the old Java folder. It's almost as if it only creates a folder with everything in it but it doesn't update the registry for whatever reason on XP. Perhaps the registry is different on 2008 R2? Perhaps a command is executed but ignored in XP? I don't know, I can't wrap my mind around it. The reason why I'd like the installer to work and do its thing is that this way I don't have to extract the zip and put everything inside the Java folder with a fake name, 'cause ok, so far so good, but I don't really like the idea to have C:\Program Files\Java\jre1.8.0_144 and inside there's 1.8.0_261 instead. I have been doing it for quite some time now, but I don't like it... it's against my mental health as I MUST have everything precise and ordered and I don't really sleep well if things are not the way I want them to be. xD

Out of pure curiosity, I tried to run the installer and then I replaced the sunmscapi.dll but it didn't work, Internet Explorer and PaleMoon were both pointing to the old 1.8.251 I had installed...

Yep, NVME.

Fair enough, what's causing it then?