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