Lost access to Python editor and interpreter

[Anonymous]

After no problems editing and running scripts since originally installing Fusion, suddenly . . .

When I select a script in the Add-Ins dialog and choose Edit, I get a fleeting message:

  Dialog Title: C:\WINDOWS\system32\cmd.exe

  Dialog Content:

        Installing extensions...

        Extension 'ms-python.python' is already installed

But . . . nothing else happens. 

Run does nothing.

Just opening a .py file in the scripts folder, opens the editor but reports no interpreter installed.

I uninstalled Fusion and Visual Studio Code and reinstalled Fusion.  Upon first try to Edit a script in the Fusion dialog, it prompted to download Visual Studio (just as it had upon original installation) and I ran the download.

No change in results.

Thanks for help here

[Anonymous]

Trying to get a completely fresh Fusion install, uninstalled Fusion, then renamed the Fusion 360 folders in AppData Local and Roaming to hide them.

Downloaded a fresh installer from my account

Installed this new download.

Now Fusion won't start.  Asks for my email and password and, after entering, get Sign in Failure; There was an error while logging in to Fusion 360

Best way to get a completely fresh Fusion installation?

Thanks

[Anonymous]

This time, hid the  Autodesk folders (one level above previous) in AppData Local and Roaming.

Now Fusion installs and runs, but . . .

Same problem with Python access as in the original post.

Anything else to hide before installing Fusion?

Thanks

[Anonymous]

Correction . . . Now (with new Fusion installation)

• Still can not edit scripts from API dialog
• But . . . scripts do run
• Create new script creates the default script which does run but can't be edited

Note: Using Windows 10

Also:  Talked with a non-Fusion user who just Installed Fusion to help me test.  Same behavior that I experience.

[BrianEkins · Accepted solution]

I'm having the same problem.  I downgraded the Python extension to the previous version and that seemed to fix it.  Seems to be an issue with the new extension so there's either a problem with it or something changed that affects how Fusion talks to it.

[Anonymous]

Brian,

Thank You.  Worked.