cosmos's community posts

Thank you for the detailed accounting of the issue. I could not see the update on May 13th. It's been more than one day since I last tried though and the update still does not show up. This definitely seems like a feedly issue, since a day has passed and the update does still not show up.

Granted, according to feedly, only one other person has subscribed to this feed. Still according to them, one day would be the maximum to re-fetch information from the site. Not sure if some https caching here is at play.

A colleague pointed out that a new version came out. Again feedly does not show it, even though the feed is set to the https link of the page.

Something seems broken there...

That did the trick, thanks!

Just tested this at home: feedly still shows the old content. I've removed the feed and then re-added it, but is still does not show the new content.

It does, but the point is that feeds are usually read through an aggregator of some sort. And feedly still does not show the latest articles.

Tried just now with my mobile, but saw no changes...

I tried to add an RSS from your page https://www.remoteutilities.com/product/release-notes.php

There's an RSS link in that page but when I added it to the RSS aggregator service I'm using - feedly - the latest version/thread presented was about version 6.6.0.7. Can you look it up? I'm using a bunch of feeds to be notified about software and especially security-related updates, and something seems screwed up here.

On failed systems there is always an event like "Product: Remote Utilities - Host -- Error 2753.The File 'rfusclient.exe' is not marked for installation."

We tried to deply 7.0.0.3 via an MSI. The result is that:
* the majority of the systems are stuck. 7.0.0.3 does not start, there is no service
* around 30% of the systems took the upgrade ok

We have been running around with this since morning. Something is seriously borked with the MSI, as produced by the online wizard.

Ι uninstalled 7.0.0.3 and reinstalled 6.10. Again I tried to install 7.0.0.3 without disabling ESET at all. And this time installation was successful! I've opened ticket #4080 for the case.