how do I block a page after I allowed it to run

Hi bpujals
 
Welcome to the Community Forums.
 
The only way that I know, at present, is to edit the text files that contains the whitelisted urls (placed there as a result of the 'Unblock and proceed' option being taken).  You should not undertake this unless you are happy to tweak your system and feel confident in your capabilities in this area.
 
If so then you can try the following:
 
1. Navigate to the following folder C:ProgramDataWRDatawrUrl (note that this is a hidden folder), and the quickest way to
    do that is to type the aforementioned path into the search field in the Start Menu).
2. In the wrUrl folder you should find a file named 'WhiteList'.  This can be edited using a text editor but note that you may    
    need administrator privileges to carry out the edit).
3. Open the file and you should see the url of the site that you previously allowed.  If you delete that line, and then save the     file, that should remove it from the white list.
 
In some cases you will need to Exit WSA, i.e., stop it running and then restart it before the revised white list is used, but I have seen no evidence of this being required when I have done this.
 
Give that a try, bearing in mind the aforementioned caveat about tweaking the system & WSA files.
 
If you do decide to have a go do let us know how it goes for you.  Alternatively, you can try Opening a Support Ticket, and asking the Support Team to block the site for you locally.
 
Hope that this helps?
 
Regards, Baldrick

Hello there, 
 
To add to what Baldrick has laid out for you, there is one other option.  In my own case, I just do not have many sites at all that I have overridden to allow instead of be blocked.  My Whitelist file only has one or two entries in it, so I tent skip editing.  I simply disable WSA, delete the Whitelist file, and then restart WSA.  WSA automatically creates a new Whitelist file upon starting if it is missing.
 
 

Hi David
 
Thanks...good tip... 😉 for those who do not have too many overrides already logged.  The only thing I would add to what you have added is that I suspect that the delete would need to be done with admin privileges...just in case and to avoid sending Windows into a frenzy as per usual when trying to delete something that it does not think should be.
 
Regards, Baldrick