Your request has been blocked

Steel Contributor

When attempting to research setting GP by script, I came across this page: 


On that page, I found this paragraph:


Additional considerations
For more information about scripting, see the Group Policy Script Center (

But clicking that link produced this response: 


Your-request-has-been-blocked.pngNeither of the reasons quoted can apply. Can anyone reproduce this behaviour? More important, can anyone explain it?


(Dev 82.0.446.0 on W10 1909 18363.720)

10 Replies

@Noel Burgess 


I get the same.


I think Microsoft need to fix the link.

Same here on Version 82.0.458.0 (Official build) canary (64-bit)

and on Firefox nightly 76a, so definitely Not Edge related issue

Getting the same on a link to GPT/bootloader info. So it's not just windows server info. Microsoft has had a habit of moving things and
Wait..I just noticed that link is from Technet script center.

it's getting retired:
"We are retiring the TechNet Gallery. Make sure to back up your code"

so that link is probably pointing to a script whose developer moved it from Technet to Github, as suggested in Microsoft's doc.


... that link is probably pointing to a  script whose developer moved it ...

That's probably the case, but I would normally expect to see an HTTP 404 'not found' response, not a snarky 'we think you're a bot, so we're not going to help you.'


There's some reason why the MSFT server involved chooses to block what appears to be a legitimate request from Edge, rather than simply telling Edge that the requested resource isn't available. 

Yes that message wasn't kinda the right one, but remember it's not telling it to Edge only, it's all browsers. I'm using Firefox at the moment and getting that error message.

@Noel Burgess 

The request is blocked.

os windows 10 
Microsoft Edge
google chrome

@Noel Burgess This just started happeneing to me. I worried. Is it temporary? will it go away? I can't contact microsoft support due to it either. 




this specific problem seems to have something to do with cached data.

try clearing cache and saved webpage files from here: edge://settings/clearBrowserData



Thanks, that solved it for me!