I’d be willing to bet some internet karma that this was a simple mistake during packaging and an errant folder create was accidentally included. I’d be incredibly surprised if any IIS components are activated by this update or if anything beyond the folder existing is out of the ordinary for the system.
No comments yet.