Unable to activate a python Venv on profile startup #11404

Open
opened 2026-01-31 02:46:42 +00:00 by claunia · 0 comments
Owner

Originally created by @leElvyn on GitHub (Nov 14, 2020).

Environment

Windows build number: 10.0.19042.0
Windows Terminal version (if applicable): 1.3.2651.0

Any other software?

Steps to reproduce

create a python venv with the python -m venv [envname]
add a profile with the commandline parameter pointing to the env script ( like C:/Users/username/pythonenv/Scripts/activate.ps1

profile :

        {
            // Make changes here to the powershell.exe profile.
            "guid": "{51b54bbd-c2c8-5271-96e7-009a87ff44bf}",
            "name": "venv",
            "commandline": "C:/Users/ordi/redenv/Scripts/activate.ps1",
            "hidden": false
        },

Expected behavior

the venv would be activated

Actual behavior

[error 0x800700c1 when launching `C:/Users/username/pythonenv/Scripts/activate.ps1']

image

Originally created by @leElvyn on GitHub (Nov 14, 2020). <!-- 🚨🚨🚨🚨🚨🚨🚨🚨🚨🚨 I ACKNOWLEDGE THE FOLLOWING BEFORE PROCEEDING: 1. If I delete this entire template and go my own path, the core team may close my issue without further explanation or engagement. 2. If I list multiple bugs/concerns in this one issue, the core team may close my issue without further explanation or engagement. 3. If I write an issue that has many duplicates, the core team may close my issue without further explanation or engagement (and without necessarily spending time to find the exact duplicate ID number). 4. If I leave the title incomplete when filing the issue, the core team may close my issue without further explanation or engagement. 5. If I file something completely blank in the body, the core team may close my issue without further explanation or engagement. All good? Then proceed! --> <!-- This bug tracker is monitored by Windows Terminal development team and other technical folks. **Important: When reporting BSODs or security issues, DO NOT attach memory dumps, logs, or traces to Github issues**. Instead, send dumps/traces to secure@microsoft.com, referencing this GitHub issue. If this is an application crash, please also provide a Feedback Hub submission link so we can find your diagnostic data on the backend. Use the category "Apps > Windows Terminal (Preview)" and choose "Share My Feedback" after submission to get the link. Please use this form and describe your issue, concisely but precisely, with as much detail as possible. --> # Environment ```none Windows build number: 10.0.19042.0 Windows Terminal version (if applicable): 1.3.2651.0 Any other software? ``` # Steps to reproduce create a python venv with the `python -m venv [envname]` add a profile with the `commandline` parameter pointing to the env script ( like `C:/Users/username/pythonenv/Scripts/activate.ps1` profile : { // Make changes here to the powershell.exe profile. "guid": "{51b54bbd-c2c8-5271-96e7-009a87ff44bf}", "name": "venv", "commandline": "C:/Users/ordi/redenv/Scripts/activate.ps1", "hidden": false }, # Expected behavior the venv would be activated <!-- A description of what you're expecting, possibly containing screenshots or reference material. --> # Actual behavior <!-- What's actually happening? --> [error 0x800700c1 when launching `C:/Users/username/pythonenv/Scripts/activate.ps1'] ![image](https://user-images.githubusercontent.com/45512739/99149490-adeaf480-268e-11eb-8724-9b57604d4677.png)
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: starred/terminal#11404