|
1 | 1 | --- |
2 | 2 | description: How to identify and troubleshoot PowerShell startup issues, including performance problems and crashes. |
3 | | -ms.date: 12/01/2025 |
| 3 | +ms.date: 01/14/2026 |
4 | 4 | title: Troubleshoot PowerShell startup issues |
5 | 5 | --- |
6 | 6 | # Troubleshoot PowerShell startup issues |
@@ -209,7 +209,7 @@ understand it's trying to do. |
209 | 209 | Steve Lee, the PowerShell Dev Manager, has a blog post that describes how to measure the |
210 | 210 | performance of your profile. It includes instructions for establishing a baseline for performance, |
211 | 211 | how to get detailed timing information, and ways to optimize your profile. See |
212 | | - [Optimizing your $Profile][05]. |
| 212 | + [Optimizing your $Profile][07]. |
213 | 213 |
|
214 | 214 | ### PowerShell 7 starts slowly in an isolated network |
215 | 215 |
|
@@ -242,13 +242,13 @@ There are three possible workarounds for this problem: |
242 | 242 | - Reduce CRL Timeout |
243 | 243 |
|
244 | 244 | Reducing the CRL lookup timeout is possible, but doing so risks other lookups to fail, that can't |
245 | | - complete in the time specified. For details about how to change the timeout, see [Manage Network |
246 | | - Retrieval and Path Validation][04]. |
| 245 | + complete in the time specified. For details about how to change the timeout, see |
| 246 | + [Manage Network Retrieval and Path Validation][06]. |
247 | 247 |
|
248 | 248 | - Remove CRL checking |
249 | 249 |
|
250 | | - The CRL checking settings are managed by Group Policy. For more information, see [Manage Trusted |
251 | | - Publishers][03]. |
| 250 | + The CRL checking settings are managed by Group Policy. For more information, see |
| 251 | + [Manage Trusted Publishers][05]. |
252 | 252 |
|
253 | 253 | > [!WARNING] |
254 | 254 | > It's possible to disable the CRL check however, it's not recommended. Disabling CRL checking |
@@ -281,18 +281,20 @@ need code that must run in **FullLanguage** mode during your profile, move it in |
281 | 281 | file that's exempted or signed. Call (don't dot-source) that script file from within your profile. |
282 | 282 |
|
283 | 283 | For more information on this issue, see |
284 | | -[PowerShell Constrained Language mode and the Dot-Source Operator][06]. |
| 284 | +[PowerShell Constrained Language mode and the Dot-Source Operator][08]. |
285 | 285 |
|
286 | 286 | ## Further reading |
287 | 287 |
|
288 | 288 | - [about_Language_Modes][03] |
289 | | -- [Measure-Command][07] |
| 289 | +- [Measure-Command][09] |
290 | 290 |
|
291 | 291 | <!-- link references --> |
292 | 292 | [01]: ../../security/security-features.md |
293 | 293 | [02]: /dotnet/framework/install/repair |
294 | 294 | [03]: /powershell/module/microsoft.powershell.core/about/about_language_modes |
295 | 295 | [04]: /powershell/module/microsoft.powershell.core/about/about_profiles |
296 | | -[05]: https://devblogs.microsoft.com/powershell/optimizing-your-profile/ |
297 | | -[06]: https://devblogs.microsoft.com/powershell/powershell-constrained-language-mode-and-the-dot-source-operator/ |
298 | | -[07]: xref:Microsoft.PowerShell.Utility.Measure-Command |
| 296 | +[05]: /previous-versions/windows/it-pro/windows-server-2008-r2-and-2008/cc733026(v=ws.10) |
| 297 | +[06]: /previous-versions/windows/it-pro/windows-server-2008-R2-and-2008/cc771429(v=ws.10) |
| 298 | +[07]: https://devblogs.microsoft.com/powershell/optimizing-your-profile/ |
| 299 | +[08]: https://devblogs.microsoft.com/powershell/powershell-constrained-language-mode-and-the-dot-source-operator/ |
| 300 | +[09]: xref:Microsoft.PowerShell.Utility.Measure-Command |
0 commit comments