Repository navigation
SCE Windows
This document provides step-by-step instructions for installing the STEM Computing Environment (SCE) on your local Windows computer. Complete the steps listed in the Table of Contents in order. Do not skip any steps.
- Check for S Mode
- Meet the prerequisites
- Prepare your personal computer
- Step-by-Step
- Quick Install
- Troubleshooting
Before setting up the course IDE on Windows, we must verify that your computer's security permissions allow you to run software developer tools. It is common for users of computers owned by others to have restricted account privileges. This simple 5-second test will determine if your machine can support local setup of the course IDE, or if you should bypass it and use just the Codio Virtual Desktop (CVD) option.
-
On your keyboard, press the Windows (⊞) + R keys at the same time to open the Run dialog box.
-
Type
ms-settings:aboutand press Enter or click OK. -
In the System > About window, scroll down to find Windows info. You may need to expand it.
-
Review the Edition line.
- No
S Mode
- No
WindowsProductName WindowsVersion OsBuildNumber
------------------ -------------- -------------
Windows 11 Pro 24H2 26100
-
On your keyboard, press the Windows (⊞) + R keys at the same time to open the Run dialog box.
-
Type
cmdinto the box and press Enter. -
Observe what happens on your screen:
- GO: A terminal window opens and shows a blinking cursor after the command prompt. Your computer's operating system likely allows local command-line tools. Recommendation: Continue with local setup of the course IDE.
Note. This test only confirms that command-line tools can open. Step 4: Install the Course IDE also requires an administrator account. If you cannot approve an administrator prompt when you reach Step 4, use the CVD instead.
- NO GO: An error popup appears, or the window immediately closes. Your computer's operating system or employer-managed security policy blocks local command-line tools. You will not be able to install or run the course IDE locally unless you resolve these issues. Recommendation: Use just the CVD. Go to the Codio README.md to configure the CVD, if you have not done so already. Otherwise, return to the main README.md to complete any outstanding tasks.
-
Windows Edition. Windows 10 or 11 Home, Pro, Enterprise, or Education not "in S Mode". What's this? How to check?
-
**Version
-
An administrator account
{{Why?}}
-
Update the operating system. How?
-
Restart the computer. How?
-
Create a restore point and label it,
Before WinGet upgrades. How? -
Open a terminal window.
- On your keyboard, hold down the Windows (⊞) key and press the X key.
- Select Terminal (Admin) or PowerShell (Admin) from the popup menu.
-
Verify WinGet. What's this?. Copy and paste the following command into the terminal and press Enter.
winget -vExpected Output: A version number beginning with
v, such asv1.29.380. Your version number will be different from the example. A different version number is normal and does not indicate an error. The key indicator of success is that WinGet displays a version number. If it does, continue to the next step.If the command does not display the expected output, follow CLI troubleshooting procedures. Do NOT continue with the remaining setup tasks until this command produces the expected output.
-
Update WinGet sources. Copy and paste the following command block into the terminal and press Enter. What's this?
winget source update
Expected Output: You should see messages indicating that all sources are being updated followed by
Donefor each source. Key indicator of success is that each source shows as Done.If the command does not display the expected output, follow CLI troubleshooting procedures. Do NOT continue with the remaining setup tasks until this command produces the expected output.
-
Update installed packages. Copy and paste the following command block into the terminal and press Enter. What is this?
winget upgrade -r -u --accept-source-agreements --accept-package-agreements
Expected Output: You should see messages indicating that {{...}}. Your output may vary. Key indicator of success is {{...}}. Note. Some updates may require a restart to complete. This is normal and does not indicate an error.
If the command does not display the expected output, follow CLI troubleshooting procedures. Do NOT continue with the remaining setup tasks until this command produces the expected output.
-
Restart the computer. How?
-
Create another restore point and label it,
Before STEM compute environment install. How?
-
Open a terminal window.
- On your keyboard, hold down the Windows (⊞) key and press the X key.
- Select Terminal (Admin) or PowerShell (Admin) from the popup menu.
-
Install Git. Copy and paste the following command block into the terminal and press Enter. What is this?
winget install --id Git.Git -e --source winget --accept-source-agreements --accept-package-agreements
Expected Output: You should see messages indicating that {{...}}. Your output may vary. Key indicator of success is {{...}}.
If the command does not display the expected output, follow CLI troubleshooting procedures. Do NOT continue with the remaining setup tasks until this command produces the expected output.
-
Install GitHub CLI. Copy and paste the following command block into the terminal and press Enter. What is this?
winget install --id GitHub.cli -e --source winget --accept-source-agreements --accept-package-agreements
Expected Output: You should see messages indicating that {{...}}. Your output may vary. Key indicator of success is {{...}}.
If the command does not display the expected output, follow CLI troubleshooting procedures. Do NOT continue with the remaining setup tasks until this command produces the expected output.
-
Install Python 3. Copy and paste the following command block into the terminal and press Enter. What is this?
winget install --id Python.Python.3.12 -e --source winget --accept-source-agreements --accept-package-agreements
Expected Output: You should see messages indicating that {{...}}. Your output may vary. Key indicator of success is {{...}}.
If the command does not display the expected output, follow CLI troubleshooting procedures. Do NOT continue with the remaining setup tasks until this command produces the expected output.
-
Install VS Code. Copy and paste the following command block into the terminal and press Enter. What is this?
winget install --id Microsoft.VisualStudioCode -e --source winget --accept-source-agreements --accept-package-agreements
Expected Output: You should see messages indicating that {{...}}. Your output may vary. Key indicator of success is {{...}}.
If the command does not display the expected output, follow CLI troubleshooting procedures. Do NOT continue with the remaining setup tasks until this command produces the expected output.
-
Open a terminal window.
- On your keyboard, hold down the Windows (⊞) key and press the X key.
- Select Terminal (Admin) or PowerShell (Admin) from the popup menu.
-
Verify WinGet. What's this?. Copy and paste the following command into the terminal and press Enter.
winget -vExpected Output: A version number in the format
v1.x.x. The key indicator of success is that WinGet displays a version number. If it does, continue to the next step.If the command does not display the expected output, follow CLI troubleshooting procedures. Do NOT continue with the remaining setup tasks until this command produces the expected output.
-
Install the STEM computing tools. Copy and paste the following command block into the terminal and press Enter to run the commands.
winget source update winget install --id Git.Git -e --source winget --accept-source-agreements --accept-package-agreements winget install --id GitHub.cli -e --source winget --accept-source-agreements --accept-package-agreements winget install --id Python.Python.3.12 -e --source winget --accept-source-agreements --accept-package-agreements winget install --id Microsoft.VisualStudioCode -e --source winget --accept-source-agreements --accept-package-agreements
Expected Output: You should see messages indicating that package sources were updated and required applications were installed, updated, or are already installed. Your output may vary. The key indicator of success is that each command completes without errors.
If the commands do not display the expected output, follow CLI troubleshooting procedures. Do NOT continue with the remaining setup tasks until this command produces the expected output.
-
Restart the computer. How?
Wiki Home · CS-Core · Ask a Question · Report an Issue
Return to a course repo: IT-140 · IT-145 · DAD-220 · CS-200 · CS-205 · CS-210 · CS-230 · CS-250 · CS-255 · CS-300 · CS-305 · CS-310 · CS-319 · CS-320 · CS-330 · CS-340 · CS-350 · CS-360 · CS-370 · CS-405 · CS-407 · CS-410 · CS-411 · CS-460 · CS-465 · CS-470 · CS-495 · CS-499 · CS-500 · CS-503 · CS-505 · CS-508 · CS-510 · CS-530 · CS-540 · CS-550 · CS-560 · CS-570 · CS-580 · CS-590 · CS-600 · CS-610 · CS-620 · CS-630 · CS-640 · CS-650 · CS-660 · CS-680
Maintained by GC-STEM.