Build 3.1.7741 shows 3.0.7741 in Help--> About

[Jillian999]

Brief description of your issue

Build 3.1.7741 shows 3.0.7741 in Help--> About

Steps to reproduce (optional)

No response

Expected behavior (optional)

No response

Actual behavior (optional)

No response

Environment (optional)

No response

[MagicAndre1981]

I have the same, so the update to 3.1.7741 is offered again and again.

[dmex]

@MagicAndre1981

The updater can't offer an update more than once every 7 days?

[MagicAndre1981]

I get the update offered again when I manually search for updates

[ToddIndry37]

I got the same bug here. I thought System Informer got upgraded to 3.1 but it's not lol.

[Almighty188]

Same issue here but not a problem for me as I don't update with the program, I download the portable bin whenever a new version comes out:

Also should update the Copyright (c) from 2023 to 2024 LOL

[Almighty188]

Anyone successfully able to update their GeoIP database in this version?
I couldn't as mentioned here: https://github.com/winsiderss/systeminformer/issues/2088

[ToddIndry37]

Oh yeah, it is! They forgot to change the copyright year on 3.1 huh. That also should gonna change too.

Sent from my iPhone 6+ lol

On 8 Jun 2024, at 08.05, Almighty188 @.***> wrote:

Same issue here: image.png (view on web)

Also should update the Copyright (c) to 2024 LOL

— Reply to this email directly, view it on GitHub, or unsubscribe. You are receiving this because you commented.

[Almighty188]

Not just in 3.1, they never updated the 2023 in all versions that came out in 2024 but since the About screen was mentioned, might as well mention it.

Oh yeah, it is! They forgot to change the copyright year on 3.1 huh. That also should gonna change too. Sent from my iPhone 6+ lol … On 8 Jun 2024, at 08.05, Almighty188 @.***> wrote: Same issue here: image.png (view on web) Also should update the Copyright (c) to 2024 LOL — Reply to this email directly, view it on GitHub, or unsubscribe. You are receiving this because you commented.

[Almighty188]

@MagicAndre1981

The updater can't offer an update more than once every 7 days?

@dmex

as the program also reports v3."0" instead of v3."1":

[kotenok2000]

It reports 3.1.0.7741 for me. Looks like someone tried to fix it but couldn't.

[Almighty188]

It reports 3.1.0.7741 for me. Looks like someone tried to fix it but couldn't.

@kotenok2000 - Talking about two different things, place your mouse pointer over the SystemInformer.exe process or the properties of SystemInformer.exe while running v3.1.7741 and what does it show for the version number? Seems like the Updater is now showing v3.1."0".7741 instead of v3.1.7741 so there is a extra 0. before the 7741. All the builds are on https://github.com/winsiderss/si-builds/releases

7741 is part of v3.1 and not v3.0 or v3.1.0 as the version numbers including builds are 3 sets of numbers not 4.

[dmex]

We're changing the build format and testing the changes before the next canary release.

[ToddIndry37]

Does this build probably fix this issue or something? Or maybe the same thing?

[kotenok2000]

no

[ToddIndry37]

Yep, I tried to update it, and it still stuck on current version. Nothing has changed.

[Almighty188]

I never use the built-in Check for updates feature as I usually just download the -bin archive of the latest available build. It seems Check for Updates for stable will show v3.0.7660 while canary will shows v3.1.12000.7441 when according to https://github.com/winsiderss/si-builds/releases/tag/3.1.7741, v3.1.7741 is supposed to be the latest stable and canary build, the first and only v3.1 build. v3.0.7660 was supposedly the last v3.0 build.

[ToddIndry37]

I never use the built-in Check for updates feature as I usually just download the -bin archive of the latest available build. It seems Check for Updates for stable will show v3.0.7660 while canary will shows v3.1.12000.7441 when according to https://github.com/winsiderss/si-builds/releases/tag/3.1.7741, v3.1.7741 is supposed to be the latest stable and canary build, the first and only v3.1 build. v3.0.7660 was supposedly the last v3.0 build.

Let me try that. If that still didn't in effect, could be they should update it soon on next build. Update: It doesn't do anything, even I install or overwrite it through the installer itself.

[Almighty188]

I never use the built-in Check for updates feature as I usually just download the -bin archive of the latest available build. It seems Check for Updates for stable will show v3.0.7660 while canary will shows v3.1.12000.7441 when according to https://github.com/winsiderss/si-builds/releases/tag/3.1.7741, v3.1.7741 is supposed to be the latest stable and canary build, the first and only v3.1 build. v3.0.7660 was supposedly the last v3.0 build.

Let me try that. If that still didn't in effect, could be they should update it soon on next build. Update: It doesn't do anything, even I install or overwrite it through the installer itself.

It is the same build because you can tell from the timestamp and that's what I am using to post all the above screenshots in this thread so it's not the build even though 7741 which is listed as 3.1 seems to itself think it is a 3.0 version. So we will probably have to wait until the next build comes out to know for sure if the updater is reporting the correct results or not since one is already on the latest build.

[ToddIndry37]

I never use the built-in Check for updates feature as I usually just download the -bin archive of the latest available build. It seems Check for Updates for stable will show v3.0.7660 while canary will shows v3.1.12000.7441 when according to https://github.com/winsiderss/si-builds/releases/tag/3.1.7741, v3.1.7741 is supposed to be the latest stable and canary build, the first and only v3.1 build. v3.0.7660 was supposedly the last v3.0 build.

Let me try that. If that still didn't in effect, could be they should update it soon on next build. Update: It doesn't do anything, even I install or overwrite it through the installer itself.

It is the same build because you can tell from the timestamp and that's what I am using to post all the above screenshots in this thread so it's not the build even though 7741 which is listed as 3.1 seems to itself think it is a 3.0 version. So we will probably have to wait until the next build comes out to know for sure if the updater is reporting the correct results or not since one is already on the latest build.

Yeah, well... guess I'll wait for the next build, and also making the kernel driver compatible with Patch Tuesday builds on Windows 10 & 11.

[Almighty188]

I never use the built-in Check for updates feature as I usually just download the -bin archive of the latest available build. It seems Check for Updates for stable will show v3.0.7660 while canary will shows v3.1.12000.7441 when according to https://github.com/winsiderss/si-builds/releases/tag/3.1.7741, v3.1.7741 is supposed to be the latest stable and canary build, the first and only v3.1 build. v3.0.7660 was supposedly the last v3.0 build.

Let me try that. If that still didn't in effect, could be they should update it soon on next build. Update: It doesn't do anything, even I install or overwrite it through the installer itself.

It is the same build because you can tell from the timestamp and that's what I am using to post all the above screenshots in this thread so it's not the build even though 7741 which is listed as 3.1 seems to itself think it is a 3.0 version. So we will probably have to wait until the next build comes out to know for sure if the updater is reporting the correct results or not since one is already on the latest build.

Yeah, well... guess I'll wait for the next build, and also making the kernel driver compatible with Patch Tuesday builds on Windows 10 & 11.

I can't use the kernel driver because it doesn't work with non-stable Windows 11 builds. Are you using the kernel driver?

[ToddIndry37]

I never use the built-in Check for updates feature as I usually just download the -bin archive of the latest available build. It seems Check for Updates for stable will show v3.0.7660 while canary will shows v3.1.12000.7441 when according to https://github.com/winsiderss/si-builds/releases/tag/3.1.7741, v3.1.7741 is supposed to be the latest stable and canary build, the first and only v3.1 build. v3.0.7660 was supposedly the last v3.0 build.

Let me try that. If that still didn't in effect, could be they should update it soon on next build. Update: It doesn't do anything, even I install or overwrite it through the installer itself.

It is the same build because you can tell from the timestamp and that's what I am using to post all the above screenshots in this thread so it's not the build even though 7741 which is listed as 3.1 seems to itself think it is a 3.0 version. So we will probably have to wait until the next build comes out to know for sure if the updater is reporting the correct results or not since one is already on the latest build.

Yeah, well... guess I'll wait for the next build, and also making the kernel driver compatible with Patch Tuesday builds on Windows 10 & 11.

I can't use the kernel driver because it doesn't work with non-stable Windows 11 builds. Are you using the kernel driver?

Yes, since it supported my Windows 11 kernel though. I don't use beta builds on here.

[Almighty188]

I never use the built-in Check for updates feature as I usually just download the -bin archive of the latest available build. It seems Check for Updates for stable will show v3.0.7660 while canary will shows v3.1.12000.7441 when according to https://github.com/winsiderss/si-builds/releases/tag/3.1.7741, v3.1.7741 is supposed to be the latest stable and canary build, the first and only v3.1 build. v3.0.7660 was supposedly the last v3.0 build.

Let me try that. If that still didn't in effect, could be they should update it soon on next build. Update: It doesn't do anything, even I install or overwrite it through the installer itself.

It is the same build because you can tell from the timestamp and that's what I am using to post all the above screenshots in this thread so it's not the build even though 7741 which is listed as 3.1 seems to itself think it is a 3.0 version. So we will probably have to wait until the next build comes out to know for sure if the updater is reporting the correct results or not since one is already on the latest build.

Yeah, well... guess I'll wait for the next build, and also making the kernel driver compatible with Patch Tuesday builds on Windows 10 & 11.

I can't use the kernel driver because it doesn't work with non-stable Windows 11 builds. Are you using the kernel driver?

Yes, since it supported my Windows 11 kernel though. I don't use beta builds on here.

That could be the variable on the whois crash.

[Almighty188]

Just noticed that this didn't get updated to v3.1.7741 as usually it is the same as the latest on github: https://systeminformer.sourceforge.io/canary.php

[MagicAndre1981]

looks like team removed that update to prevent users to run into the update showing again issue.

[Almighty188]

Looks like on https://github.com/winsiderss/si-builds/releases - v3.1.7741 got removed as v3.0.7660 is the latest version shown.

[MagicAndre1981]

works now with 3.1.24184.1 (3aab5576)

So this can be closed