Closed Redsandro closed 7 years ago
@ MSDN
Blocked Command execution is blocked (on user input host calls etc)
I have never seen that. I added that warning in case it appears later. Jobs are left in the job queue after AU exits. You can examine them with job cmdlets (get-job , receive-job and friends).
I am not sure why it happens. Updaters look normal. You should really do that on AppVeyor because it is a reference machine for which I can download execution logs and inspect.
Thanks for looking into it. It appears to be some basic UAC-type blocking for security reasons. After launching vagrant, I need to Set-ExecutionPolicy Bypass -Scope Process
* and it works fine.
*) Set-ExecutionPolicy unrestricted
does not help.
You should really do that on AppVeyor
Yes I should. One step at a time. I don't like copy-pasting without understanding, especially when it is powerful, posts gists, has full git control, even over some private 'organisations' that I cannot seem to opt out, and does public commits. I don't know what I need to take into account to prevent it from publicizing my private repo's, api keys, mothers' maiden name, girlfriends private pictures and the location of my baseball card collection.
Glad to see you solved it. I do bypass on system initialization on new machine. I never disable UAC tho.
AV is all taken care off in secure manner :). That was my highest priority when implementing it. Of course, you can set it in unsecure way by mistake.
I'm trying out
updateall
with someau
packages. I should use a script for that, but I like to try stuff one step at a time.Here are some problems:
I'm not very proficient with Powershell (or Windows, for that matter). Do you have an idea what causes this?