wizardberry

I ran into this problem where we had two DCs, upgraded in-place for both of them to 2019, detested the idea of reintroducing a 2016 box into the mix and demoting then re-promoting. The tell-tale was the dfsr 367 error message about not being able to instantiate robocopy with createprocess() - as seen in the dfsr log files in c:\windows\debug. So here is the ultimately workaround to that! Copy DFSRS.exe from a windows 2016 box to your windows 2019 boxes, take ownership and permission of the 2019 dfsrs.exe file in system32, stop the dfs service, temporarily rename the dfsrs.exe in system32 to .old, copy the 2016 version in there and start the service again. Do this on both servers...no other dlls or dependencies are necessary. Run through all the setglobalstate commands and watch till it is done. Then swap the dfsrs.exe back to the 2019 and call it gooooooood!!!!