The prerelease update this morning to re-enable firewall checks 2023.03.01.1511 brought back the stuck at System Firewall check and Settings page not loading. I uninstalled it and loaded the stable release 2023.01.23.1746 and it works.
1 Like
Updated to v2023.03.02.0558. Still seeing same CPU load 11-12%. Settings page works.
1 Like
I updated Channels to 2023.03.03.1951. My CPU load increased. It is now bouncing between 12.9% and 14%.
I used Task Manager to stop Channels, then reloaded. CPU load remained high. The setting page does still load with new update.
FYI.
Thanks for the Powershell fix. I had the same exact issue, now resolved.
2 Likes
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.
For those still seeing high cpu, do you have the Tailscale feature enabled?
1 Like
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.
Can you try the latest prerelease
1 Like
31 %cpu just watching a channel no transcoding. Running as service.
Logs have been submitted as 663e5dbd-8014-42be-8687-d6175b799da2 .
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.
Mine also went down to less than 3 Percent also after updating windows. Thanks for posting about the updates.
2 Likes
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
anyone?
I would but I never had a problem accessing the Web Server.
Never had a prob here.
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
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.
1 Like
This topic was automatically closed 365 days after the last reply. New replies are no longer allowed.