382 votesPaul Anderson commented
So at least two years have passed since this problem was first observed and MS haven't fixed it. In my experience with MS systems, if an issue remains unresolved for this long it will never be resolved. Give up folks. Microsoft don't care. I'm going to recommend we switch our new server baseline from 2016 to 2019.
Would be interested in understanding the scenario where you are using the cmdlet & specifying the reason for rebooting. To explain: our previous assumption was that users would EITHER use the server UI that captured this information, OR use the cmdlet (often so they didn’t need to supply that reason text).
So, what would help is to understand in what situations the cmdlet is being used and specifying the reboot explanation is desirable.