From 6ef1e5637b3cc63af3b02eeea9d0f804e63a5e14 Mon Sep 17 00:00:00 2001
From: Chad Wilson <chadw@thoughtworks.com>
Date: Fri, 13 Dec 2024 20:42:10 +0800
Subject: [PATCH] Fix broken link

---
 .../2015-06-13-using-windows-powershell-tasks.html.markdown.erb | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/source/posts/2015-06-13-using-windows-powershell-tasks.html.markdown.erb b/source/posts/2015-06-13-using-windows-powershell-tasks.html.markdown.erb
index 731b52636f..e25a68db85 100644
--- a/source/posts/2015-06-13-using-windows-powershell-tasks.html.markdown.erb
+++ b/source/posts/2015-06-13-using-windows-powershell-tasks.html.markdown.erb
@@ -138,7 +138,7 @@ or an external process call fails:
 ### See also
 
 [PowerShell execution policy](https://learn.microsoft.com/en-us/powershell/module/microsoft.powershell.security/set-executionpolicy)
-[Bypassing PowerShell execution policy](https://blog.netspi.com/15-ways-to-bypass-the-powershell-execution-policy/)
+[Bypassing PowerShell execution policy](https://www.netspi.com/blog/technical-blog/network-penetration-testing/15-ways-to-bypass-the-powershell-execution-policy/)
 [Setting execution policy directly in the registry](https://codelucidate.wordpress.com/powershell/change-execution-policy-in-the-registry/)
 [GoCD PowerShell runner plugin](https://github.com/manojlds/gocd-powershell-runner) - I believe it can only be configured on Windows based GoCD servers