Windows uninstaller might still leave a broken `AutoRun` registry entry

[jaimergp]

But, why not use the same method as conda init --reverse? That might be more robust to upstream pattern change.
Moreover, it seems that current method will break AutoRun with value like <Conda AutoRun> & <Other App AutoRun>, by substituting it to & <Other App AutoRun>. But it is invalid to have beginning & in CMD.exe

Originally posted by @YouJiacheng in #521 (comment)

[github-actions]

Hi there, thank you for your contribution!

This issue has been automatically marked as stale because it has not had recent activity. It will be closed automatically if no further activity occurs.

If you would like this issue to remain open please:

1. Verify that you can still reproduce the issue at hand
2. Comment that the issue is still reproducible and include:
   - What OS and version you reproduced the issue on
   - What steps you followed to reproduce the issue

NOTE: If this issue was closed prematurely, please leave a comment.

Thanks!

[FaustinCarter]

This actually bit me just a couple days ago! Took me ages to figure out why cmd.exe refused to start. Broke basically everything that relies on a batch script to launch (looking mostly at you, VSCode).

This is on Windows 10 LTSC. Once I deleted the offending registry key, everything was back to normal.

[marcoesters]

This should be closed by #897 and #1069