Oscar Romero  - This morning the recently renewed Helpdesk page reported 9.5.0.18 was out, but when I clicked the link (help.kaseya.com/.../RN) for the Release Notes it stops at .17. This time I clicked your forum post link and that (help.kaseya.com/.../RN) does work because it links directly to the Release Notes for patch .18. Someone needs to update the list of patches in the first link.

And another thing I already noticed before. When I open the Community Forum and login I end up at Browse Forums. After sorting on Last Post your Forum post on patch .18 isn't visible. Only when you open the Discussion Forums at the top of the page you see this recent post. Is there a good reason for this, or is it a lack of indexing? When I check the Patch Release forum in the list of all forums it still shows the previous post from the 14th as the last post... I noticed this before, but since it impacts how you use the forum it's good to give it some attention...

OudjesEric  the index does need to be updated.  Great catch.

As for the system patch posts specifically, that is a permission update which needs to be validated.

Okay Oscar Romero  - It's almost correct, after opening help.kaseya.com/.../RN the left list of the Release Notes with R95 Patch Releases is now showing patch .18, the main window on the right still only shows up to patch .17.

I'm not sure what you mean by the second sentence. To me it's not working correctly if you can see recent posts by choosing Discussion Forums, but can't see them if you list all forums sorted by last update. I wasn't really aware of the difference, but consider it an issue.

patch 9.5.0.18 now identifies The Windows Server 2008R2 OS as "<2003" which causes many scripts to fail.

Oscar Romero Hi All, This patch 9.5.0.18 is causing some big issues and I would caution anyone from installing it tell Kaseya has found a fix. I have an open ticket with them now on it. The issue is that if you have an older server OS like 2012, 2011, and 2008 after the update the server may then Identify its operating system as <2003 and then procedures will no longer run on them, this also makes it so that Acronis Backups no longer run (Big Issue!) also you can not install, remove or verify the install of Acronis.

Oscar Romero Can you verify this and update us.

I'm not seeing this issue on my demo vsa which I updated last week but I only have one 2008R2 agent there. Did you guys ran reapply schema manually after the patch?

I was gonna update our production vsa today but I think I'll wait for Kaseya's official response.

neuvoja Yes, I ran reapply schema and this did not fix the issue. Also this is not affecting all of the 2008 servers  it seems to be random some that I have are working fine. I would not update at this time.

I also have the "< 2003" OS issue. We see it on 2008R2 and SBS 2011 machines. (2012 reports properly). Kaseya Support responded that they are aware of the bug in the VSA and are working towards a solution/fix.

Hi All, Patch 9.5.0.18

Kaseya Support has updated my ticket and has confirmed that it is a bug and that they are working on it.

Hello Ron,

Thank you for contacting Kaseya Support, my name is Donald White and I will be the technician assisting you with this ticket.

I understand the urgency of your case and we are working to find to root cause and remediations for this issue.

We have identified this as a bug in the software, and have seen other incidents similar to yours.

I'll keep you updated on this case, and as our engineering team works through this issue.

Thank you for your patience.

Best Regards,

Donald D. White | Customer Support Engineer

Kaseya Support

Patch .18 seems to be pulled at the moment. My VSA isn't reporting this as available anymore.

I was wondering if Kaseya shouldn't be doing that and this time they actually did. Good to see Kaseya behave responsibly to their customers who haven't already installed this patch...

When i search for latest update it just states the latest is 9.5.0.17 even though i am already on 9.5.0.17, also if i run kinstall on the server it does an upgrade but says the same thing 9.5.0.17 upgrade to 9.5.0.17, goes through the normal process, when i log in its still 9.5.0.17 ???

i think it has been pulled do to a bug

We've opened a ticket as this affected ~20 of our clients and their BUDR. Engineering gave me a call to let me know it could be up to 2 weeks to develop a fix and in the meantime to manually set each client up with a backup using the Acronis Console. Not very happy that this is requiring hours of our labor.

techworks , Thanks for the update, I know your pain.