It's pretty random that an arbitrary number of reboots up to 15 times fixes the issue.
That sounds like there is either:
- some kind of upstream issue with deploying a fix (so most of the reboots are effectively no-ops relative to the fix)
- some kind of local reboot threshold before the system bypasses the bad driver file somehow.
The former I can see because of the complexity of update deployment on the internet, but if it's the latter then that's very non-deterministic behavior for local software.
My first thought on hearing "15 reboots" was it being a means for Support teams to task users with busy-work, buying them time for further troubleshooting before the avalanche of supports requests came back to them.
Then my second thought was frequent rebooting to fill activity logs, possibly push a suspicious action/trigger performed by CS off of the log.
That sounds like there is either:
- some kind of upstream issue with deploying a fix (so most of the reboots are effectively no-ops relative to the fix)
- some kind of local reboot threshold before the system bypasses the bad driver file somehow.
The former I can see because of the complexity of update deployment on the internet, but if it's the latter then that's very non-deterministic behavior for local software.