Try adding USER root before the mkdir.

Also, just in general, when debugging container files, I comment out the failing line and set my command to tail -F /dev/null, then you can build and run the container and exec <container> bash and try to manually run the commands that are failing.

Just switch to GNU/Hurd

/s

This is what I was thinking. For a first iteration to get out the door immediately it could just be windows with a “game browser” that launches full screen when you turn it on 😂

No they’re not. And the tech literate people that will see that they can disable this protection and continue as normal.

Microsoft doesn’t always do good things, but I think this is fine. If you open firefox it’ll ask you if you want to set your default browser, and it won’t regedit for you. It will open up the proper windows menu that lets you set firefox as the default.

Not letting malware change your settings by default is a GOOD thing. It is also a good thing that advanced users can disable the feature.

The only bad thing about the story is the lack of transparency. Having to find out about it by breaking tools is bad. It would be better if they had a changelog for these updates that say what they do so admins can see if their tools will be affected.