Dave-H

I've been experimenting with your SysTrayUtil program. I've been using PSTrayFactory for some years to organise the system tray and remember where icons are, but thought I'd try an alternative. It seems to work OK, but there are a couple of icons which don't seem to appear in the HKEY_CURRENT_USER\Software\SysTrayUtil "Order" entry. One is the icon for Trusteer Rapport, and the other is for the Eudora e-mail client. That being the case I can't reorder them as I want.

As I'm sure you realise, English is not @heinoganda's first language, and many of their posts are therefore a bit strangely worded and need a bit of interpretation! I will add the note about Vista, but of course the tool was originally only intended for use on XP, where admin rights are not an issue. I've also reworded the section you mention to make it clearer (I don't know what "loud" was supposed to be either!) I hope what it says is now correct!

That's interesting, perhaps only earlier versions of the updater used that registry entry. I'm afraid only @heinogandacan answer that question, and they don't seem to be around here any more. I do use ProxHTTPSProxy, but I'm not sure that's relevant as it's set to work only with https connections.

I'm getting the same "access denied" on that URL too if I enter it in my browser. The URLs in the registry entry for the updater seem to redirect to that, and yet the updater works for me!

I know you're very tight on security, do you have that URL blocked somewhere? I notice it's http, not https.

Ah right. This is what your registry entry for the updater should look like. Windows Registry Editor Version 5.00 [HKEY_LOCAL_MACHINE\SOFTWARE\Cert_Updater] "Version"="1.6" "SST_Download_URL"="http://wsus.ds.download.windowsupdate.com/msdownload/update/v3/static/trustedr/en" "SST_Download_URL_D1"="http://ds.download.windowsupdate.com/msdownload/update/v3/static/trustedr/en" "SST_Download_URL_D2"="0" "SST_Download_URL_D3"="0" "SST_Download_URL_D4"="0" "SST_Download_URL_D5"="0" "max_number_of_download_attempts"="30" "file_for_settings_URL"="0" "log_file_enable"="0" "end_timer"="0" "AUTHDATE"="20210910" "DELDATE"="20210910" "ROOTDATE"="20210910" "UPDDATE"="20210910" "DISALLOWEDDATE"="20210316" "Last Update Roots"="06/10/21 22:35 Status OK" "Last Update Revoked"="06/10/21 22:35 Status Ok" "webspider_to_compare"="1" If it's the same, I don't know why it would be looking in those strange places! Cert_Updater.reg

That's very strange! Did you import the registry file that came with the package? As far as I know that sets the download URLs.

In many areas I don't think it's that different to Windows 10. I wouldn't say it was worse or better, just different! I'm sorry about the loss of the live tiles in the start menu though, for some apps I found them very useful.

Yes, those files are working fine here too, on YouTube, Instagram, and Facebook. I've disabled the Primetime plugin. I'll report back if I find any downside to using the files instead of the plugin, but all looks good at the moment. Thanks, Dave.

Done.

Thanks, I'll give those files a try!

No problem @mixit! Thanks very much for responding anyway. Just as an aside, I've now found that I can still post to Instagram OK using Firefox 52.9, I just can't see the list of previous posts any more. Cheers, Dave.

Well the Instagram videos are still working fine for me, so I doubt that anything has fundamentally changed in that area. If it has, the Primetime module is still coping with it on Firefox 52.9 ESR, as it is on Facebook and YouTube!

Yes, it was mixit who fixed the videos problem. Let's hope they're still around to look at this issue!

Thanks @Dixel Useful to know that those options are available, certainly if Instagram break compatibility with Firefox 52.9 even more in the future! At the moment though everything seems fine apart from reading the earlier comments (the last few are visible under the posts anyway, it's just the "see more" pop-up window which is malfunctioning.) When the videos stopped working a while ago, someone came up with a script hack to fix it, I was rather hoping that this might be the same!

Has anyone else still using Firefox 52.9.x ESR noticed that the Instagram comments are no longer displaying? It was fine until a few days ago. Now although the comments dialogue appears correctly there are no comments actually displayed, just a blank white area. I've tried several different user agent strings, but nothing seems to make any difference.

Thanks, glad I'm not the only one seeing this! In my experience the new post is always actually saved and posted, it just doesn't tell you that and you don't see it until you refresh the page.

There appears to be a slight issue with Status Updates. If you add a reply and send it, the button says "sending" but then stays like that. The new post has actually been saved, as can be seen by refreshing the page. Seems to be the same in all the browsers I've tried. 🤔

Thanks! No repeat of the "out of memory" error this time. I did have Firefox 52.9.1 ESR running, but with no tabs open.

UHD videos work fine for me on Firefox 52.9.1 under XP. I realise this isn't with a Chromium browser of course, but it shows that XP itself is not the problem.

I suspect that the EU flag was probably dropped in the new version of the forum software, and it defaulted to France as it's what it thought was the nearest equivalent! If you want to change that I guess you'll have to set yourself as being in the UK in your profile.

What country are you actually in? The flag should surely follow the country stated in your profile.

I would certainly have had Firefox 52.9.1 ESR open when I tried the updater, but I couldn't say for certain whether it had any tabs open at the time.

Well that's good to know, I guess it must have been just a glitch on my system at the time that I ran it.

Just ran the @heinoganda updater today and saw this for the first time ever. Slightly worrying, but when I said yes, it still seemed to work OK. Anyone any idea why it would have appeared, I'm certainly not obviously short of memory, but presumably this is low-level memory, not RAM.