We have coordinated this report to our Product Development Team to investigate on this issue. We thank you for bringing this to our attention. We will provide an update shortly.
Question: I do see that somehow this nasty KB4284826 did get deployed to two PC’s. Can Comodo “Uninstall” patches that it installs?
Edit: never mind, I just remebered I can probably use a Procedure to get this pulled out??
Yes…I have now Blocked this KB, and am trying to figure out the Procedure. However, where do I locate the cryptic number after the KB # the script seems to refer to??
Hello @howie
The script needs to be run twice. As mentioned in the Description, the first time you run the script, it will show a list of KB updates. Look for the KB4284826 entry. The ‘cryptic number’ after ‘KB4284826~’ will be the one you need to assign to ‘kb_list_user’.
The actual removal process of the KB update will occur on the second run.
I have seen the same thing a few times already and we just started to test the platform.
Why is this an ongoing problem?
I have several computers now with multiple patches in different language installed.
So I need to run the script twice on each computer for each wrongly installed patch?
I cant hide the patches so whats the process to make sure they dont show up in your list and dont get installed again?
The reason for this issue is Windows distributes the same patch ID for the same package with different languages. On our side, Patch ID is associated with first record on master patch database. If the first patch definition that was entered to master database is English or on any other language, current system returns that definition for that Patch ID to all ITSM instances.
While this is a cosmetic issue–it will still install the right package for the endpoints. We have forwarded your report to our Development Team to investigate its root cause.
What our developers require are information from the endpoints where the issue have occurred (one or two endpoints will be enough ) so we can have them look at the data concerned.
We would like to reiterate that we assume that you have updated the Comodo Client Communication (CCC) agent on your endpoints as well. A support ticket had been created for your report.
Please check your forum registered email for some data we require for investigation.
Thank you for the quick response.
I did respond to the ticket with the requested information.
Thank you. We will provide you an update with Our Developers output as soon as possible.
To all,
Our Product Development team had informed us that the fix for the reported issue where “Foreign Language Patch Names in ITSM Patch Management” has been completed and will be deployed on September 22 release. We at Support will keep you on the loop for any update on this issue.
We have also sent an individual email for the update.
Thank you.
Hi @smartcloud, thank you for informing us. We will advise development team on this issue.
Hello @stevens_pete
The issue should have been fixed but if you are still having the same issue. We have created a ticket for you in order to investigate this issue further.
With best regards
Our Development Team is taking measures to get this issue resolved. They are currently redesigning the method of this functionality and will include you on the report. We will be reaching you via support email for additional portal account information.
Just to bring this back up, I’m still seeing foreign language updates in Patch Management.
Hello @PromptCare , We have informed our ITarian Team to review your reported issue and get back to your case as quickly as possible.
I doubt it… it seems to have been ongoing since 2017!
Hello @chris_h ,
We regret for the inconvenience. Our Development Team is still working on to get this issue resolved. We will get back to you once we get an update on this.
still ongoing, today i have it.