This is split from Problem updating from 41.20250108.0, and a fix (after some troubleshooting) - #32 by siosm because it is a different issue. Considering its as dedicated issue increases the likelihood to get it solved
1 Like