# Windows Setup Environment

{% hint style="info" %}
**To open a Command Prompt in WinSE, hold down SHIFT + F10**
{% endhint %}

#### When you boot a computer using Windows 10 Media, you are booting to the Windows Setup Environment.  I refer to this as WinSE (yes, just like WinPE and WinRE).  WinSE exists as Index 2 of the Boot.wim

![](https://3420392058-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2F-LpnxLqvh8u2fEz86kIM%2F-Lq-eK7gUWW64n_QwEIC%2F-Lq-eeaE1Xx6HesXb4x3%2Fimage.png?alt=media\&token=4930a6d4-82d3-4dbe-80e9-ff378a8884a5)

## PowerShell and OSD Module

#### Through the Magic of Offline Servicing, I can add PowerShell to WinSE (OSDBuilder helps) and start doing some fun stuff.  Using the magic of OSDBuilder ExtraFiles, I decided to add the OSD Module to WinSE so I can have some fun.  Here is where you need to save the OSD Module

```
<Mount>\Windows\System32\WindowsPowerShell\v1.0\Modules
```

![](https://3420392058-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2F-LpnxLqvh8u2fEz86kIM%2F-Lq-eK7gUWW64n_QwEIC%2F-Lq-fFz515db3KHIczNO%2Fimage.png?alt=media\&token=47c4235c-c8d0-496b-8faa-9a3f4a84e452)

## ExecutionPolicy Restricted

#### Unfortunately WinSE's PowerShell Execution Policy doesn't help me out because this prevents the loading of PowerShell Modules.  I'll detail in the next page how to take care of this

![](https://3420392058-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2F-LpnxLqvh8u2fEz86kIM%2F-Lq-eK7gUWW64n_QwEIC%2F-Lq-fn1XwEDThSBRd6qQ%2Fimage.png?alt=media\&token=debd8477-f996-4ab3-867d-3054d5d8fbc4)