Same issue here. Please alert when someone has a solution for this.
I have been in contact with an engineer from Microsoft for the last 2 months or so about this. Apparently, a Lead Technical Advisor has yet to actually mark this as an "issue", so it is not allowed to be escalated to the senior engineers in order to be solved....
Microsoft this is an issue and needs to be resolved. Holding back my 1903 deployment rollout because of this small but major issue.