High Windows CPU Usage With Latest Windows Update

[cahillbill]

Thanks for the Powershell fix. I had the same exact issue, now resolved.

[anderst33]

About 3 days ago the CPU load from Channels disappeared with the same version v2023.03.02.0558. Seems like it was after a reboot for another reason. Didn't notice the improvement until the next day. This version seems to not do firewall checks.

[tmm1]

For those still seeing high cpu, do you have the Tailscale feature enabled?

[djw]

FWIW, I have been running the Win10 pre-releases for a week or so. No appreciable CPU load at all.

Tailscale is enabled and has been.

[tmm1]

Can you try the latest prerelease

[Edwin_Perez]

31 %cpu just watching a channel no transcoding. Running as service.

Logs have been submitted as 663e5dbd-8014-42be-8687-d6175b799da2 .

[loucille48]

I have updated to version 2023.03.28.1656. My CPU usage is 1% or less, even with viewing Channels on my TV. However, the CPU usage was corrected for me on my PC in the updates earlier this month.

[Edwin_Perez]

Mine also went down to less than 3 Percent also after updating windows. Thanks for posting about the updates.

[tmm1]

Looking for a guinea pig.. someone who had issues with the Settings page not loading before, and can try a test build. I want to re-enable the firewall checks and see if its still happening after the other recent changes.

To try it out:

curl.exe -XPUT http://127.0.0.1:8089/updater/check/2023.04.07.0137

[tmm1]

anyone?

[Edwin_Perez]

I would but I never had a problem accessing the Web Server.

[troyhough]

Never had a prob here.

[anderst33]

I had the Settings page issue. Is there are a way to revert back to a prior version that works for me if that test build causes issues? Such as running:

curl.exe -XPUT http://127.0.0.1:8089/updater/check/2023.04.05.1931

[tmm1]

Yes you can revert using:

curl.exe -XPUT http://127.0.0.1:8089/updater/check/2023.04.09.2151

[anderst33]

Sorry for the delayed reply. I just updated to test build 2023.04.07.0137. Settings page loads right up. All Troubleshooting checks pass where they would stop before at System Firewall. No CPU load. Looks good. I'll run this for a few days if any other issues appear before updating to a later release.