View Issue Details
|ID||Project||Category||View Status||Date Submitted||Last Update|
|0005655||SUMo||Bug||public||2019-08-20 18:12||2019-08-26 14:05|
|Target Version||Short term||Fixed in Version|
|Summary||0005655: When querying SUMo server for a false major update record, it reports needing an update|
|Description||After performing a deep scan and check operation with SUMo 220.127.116.116, it reports that Microsoft Edge isn't up to date. It finds version 11.0.18362.267 locally installed. It claims existence and availability of major released update to version 18.104.22.168. According to my knowledge, this is a not yet released version but a beta version instead. And I haven't enabled beta reporting!|
When looking up if SUMo server recognizes its error of undue reporting, I find the next error on SUMo server about the version of SUMo itself. The server considers my SUMo version 22.214.171.1246 as being version 126.96.36.1993, requiring an update to version 188.8.131.526. SUMo client doesn't see a need for such an update as it considers its version 184.108.40.2066 as up to date.
|Tags||No tags attached.|
||Do you have both versions of SUMo on your system ? Therefore, it's a known weakness (like update status when multiple local versions are detected)|
What do you mean when asking if I've both versions on this system?
This report comes of the registered and installed version 220.127.116.116. It's the only installed version. Why should other non-installed versions impact this installed one when running the installed one?
When I sort the SUMo report to product name, I can confirm that the SyMenu portable framework is still at SUMo version 18.104.22.1683 and the PortableApps framework still at SUMo version 22.214.171.1245. All three are on this system. These portable ones aren't in the search patch. And I guess that they aren't in the Windows registry as they've not been installed. They may not be found within the Windows search path (for the console program) neither.
This situation exists already for months that I've these two portable instances and an installed instance (since June 2019). The portable instances don't get updated so quickly by these frameworks. PortableApps framework is quicker in updating than SyMenu. The reported behaviour appeared a few months ago and lasted only a few days. Now this same symptom returned. If it's a known weakness, why doesn't it happen all the time but instead only some sporadic intervals?
||I mean : do you have both 5.9.6 and 5.9.3 presend on your system (installed, or portable). If yes, that's a know issue.|
As already written: Version 126.96.36.1996 is installed, running and reporting on that machine while version 188.8.131.523 is present as portable instance on that same machine.
So you say that this is a known issue. Then, I'm wondering why I see this phenomen not permanently?
And it happens when I lookup Microsoft Edge on SUMo server. I didn't lookup SUMo itself on SUMo server.
||And it seems, I forgot to attach the screenshots.|
The fact that the problem is not permenent is fully understood : when last "check" in done on 5.9.3, servers "thinks" that you're on 5.9.3, and therefore indicates that an update is required.
next time, if latest check is done on the 5.9.6, the message will no longer appear
||Side effect of 0002373|
|2019-08-20 18:12||wolf||New Issue|
|2019-08-20 18:18||Kyle_Katarn||Assigned To||=> Kyle_Katarn|
|2019-08-20 18:18||Kyle_Katarn||Status||new => feedback|
|2019-08-20 18:18||Kyle_Katarn||Note Added: 0003680|
|2019-08-20 19:38||wolf||Note Added: 0003682|
|2019-08-25 16:06||Kyle_Katarn||Note Added: 0003686|
|2019-08-26 08:06||wolf||Note Added: 0003689|
|2019-08-26 08:23||wolf||Note Added: 0003691|
|2019-08-26 14:04||Kyle_Katarn||Note Added: 0003692|
|2019-08-26 14:04||Kyle_Katarn||Relationship added||related to 0002373|
|2019-08-26 14:05||Kyle_Katarn||Status||feedback => acknowledged|
|2019-08-26 14:05||Kyle_Katarn||Note Added: 0003693|
|2019-08-26 14:05||Kyle_Katarn||Target Version||=> Short term|