NEW bug - 1.18 version is unable to check for updates

[Naki]

Using latest Windows 10 Enterprise version, ver. 22H2, 64-bit OS, with all Windows Updates installed.
My CPU is Intel Haswell, Core i3 w/HT - 2 cores/4 threads. 16 GB of DDR3 RAM. Crucial SSD (with lots of free space) + 2 Seagate HDDs.

Checking for updates shows this error -->

Screenshot 2022-12-09 14.40.58.png

I noticed somehow no entry exists for Core Temp in Windows Defender Firewall, so added one with Network allowed chosen as Private.
No change, still get the same error?
If it matters, I am using Microsoft Hyper-V on this PC, which has added some virtual network adapters/virtual router.
Any ideas/comments, please?
(I will also check my HP laptop in a bit.)

NOTE: Older, previous Core Temp version had no such issues - it worked fine with Check for updates.

[The Coolest]

A change was made in the structure of the HTTP request that Core Temp sends and in my testing it worked correctly.
I'm not sure why it's not working for some people, but it will be fixed soon by reverting this change back to the previous implementation.

[Naki]

A change was made in the structure of the HTTP request that Core Temp sends and in my testing it worked correctly.
I'm not sure why it's not working for some people, but it will be fixed soon by reverting this change back to the previous implementation.

Great! Thanks for the info & update. Looking forward to the fix.

By the way, same issue happens on my HP Workstation laptop - it runs Windows 11 OS. (again, ver. 22H2)

[The Coolest]

I think this failure may be on the ISP level or router? If it's not the firewall on the machine, it must be something else.

[Naki]

I think this failure may be on the ISP level or router? If it's not the firewall on the machine, it must be something else.

Router is a fairly new TP-LINK-something, one of those with WiFi-6 (aka WiFi-ax) support.
It may have a firewall built-in, but I am not sure if it is enabled, or how to configure it.

Also, I think I changed from my ISP provided DNS servers to Open DNS in router settings.

Anyway, previous Core Temp version Check for updates worked fine, this one does not.

[JaY_III]

Also seeing the same thing on my end.

Disabled Local Machine Firewall -> same error
No block I can see on the firewall (opnsense)
Upstream DNS is Quad9 using DNSSEC
ISP : Bell Canada Fiber

[Nox]

I am observing the same issue after updating from version 1.17.1 to 1.18. And I can confirm that Check for updates worked with 1.17.1 - I've just updated now.

[Fuzzilla]

I have rolled back to 1.17.1 as it's update checker is functional. The checker in 1.18 fails. This was done to easily check for update 1.18.x.
I can launch 1.17.1 and check for updates, close software. Load 1.18, fail an update check, close software. This process can be repeated in any order. Both versions were on the same machine at the same time. No system settings or router/modem/gateway settings were changed.
Hope this helps.

[root]

Same problem - version 1.18 can't find updates, on two different laptops!
and tell me how you can roll back to the previous version 1.17 or where to download earlier versions? ( just in case)))

[brucemc777]

I don't know if this is your bug or mine!

I know i have an active internet connection, if for no other reason i am here; Core Temp is not able to check for updates. I never (knowingly) set up a rule to block either outgoing nor incoming communications. Attached are that which i block through Glasswire, if it helps-

GW.png

(I just block that MS stuff as i see it as superfluous).

What can i check (please be as precise as possible, i just know enough to get myself in trouble) to try to resolve this issue?

Thank you for your help,
-Bruce

[Fuzzilla]

Hi brucemc777,
Nothing to check it is not your system. 1.18 is bugged this way for many people, the developer has not yet fixed this.
You can download version 1.17.1 at the CoreTemp homepage under More Downloads/Past versions I believe, this will not have an installer. 1.17.1 with an installer can be found on the net at a few reputable sites, just do a Google.
FWIW a noti for your post didn't arrive until three days ago, though it appears you posted this on March 10th.
Hope this Helps

[Naki]

It has been quite a while?
Any plans to fix the bug before this summer, or in the summer?

[Naki]

It has been quite a while?
Any plans to fix the bug before this summer, or in the summer?

Any updates, please?

[Naki]

It has been quite a while.
Any updates, please?

[Naki]

It has been quite a while.
Any updates, please?

All fixed now in new 1.18.1 version! Thanks.

[Fuzzilla]

Confirmed working update routine. Thanks!