You're responsible for your own career.
During the next calibration call, your manager can't be like, "well he spent 8 hours each week resetting up his machine after a reboot, so we need to give him credit for that too."
Your job is to deliver impact, not fight system configurations.
Maybe you’re not gonna get fired, but I can’t imagine someone hitting staff level because they spent a third of their week recovering from a weekly reboot
Person A: Not able to accomplish anything because security blocked essential... Person B: Shipped product F, look at this impact to our KPI. Saved costs by retiring service C. Mentored little jimothy.
Who get the base salary bump and bonus allocation in that scenario
Do we promote this guy? Do we fire this guy?
It doesn’t matter what the excuse is or the size of the company, if you don’t have impact for the next level you’re not promoted. Put simply, you’re not getting promoted rebooting your machine.
Maybe your boss can defend you from a conversation, especially if the problem is systematic (impacting the whole team).
I suppose filling out a ticker or two every day and constantly bothering IT non-stop might be rhetorical best option (assumings one has enough energy for that)