[–] [deleted] 0 points 2 points (+2|-0) ago 

[Deleted]

0
0

[–] matthewlinton [S] 0 points 0 points (+0|-0) ago 

It sounds like your issues with Windows Update configuring updates every time you reboot is fixed. I've actually seen this behavior before where WU misbehaves until you've run it several times. Usually this results in WU hanging for a very long time.

Has Ancile correctly hidden updates? the log file you posted stops at the beginning of uninstalling updates.

Now that things are working better, you may want to try deleting Ancile, re-downloading it, and re-running it. without making any changes to "config.ini" at first. Just to make sure stock Ancile is working correctly. After that run you can disable the hosts file editing. Don't worry about running Ancile multiple times, that won't break anything.

[–] [deleted] 0 points 2 points (+2|-0) ago 

[Deleted]

0
1

[–] matthewlinton [S] 0 points 1 points (+1|-0) ago 

It sounds like Ancile is un-installing Windows updates, but not actually hiding them. If you're part of an Active Directory domain (i.e. logged into your work PC), your SA may have disabled the ability to hide updates. If this is your home PC that shouldn't be the case.

The "configuring updates" message is normal after uninstalling some Windows updates, but you shouldn't get the "update failed" message. However, I've never tried running Ancile on a fully updated system to see what happens when you uninstall everything at once.

You can manually delete Windows updates which are stored in "C:\windows\software distribution\downloads",but it's recommended you use the disk cleanup utility.

Next time you run Ancile, you may want to check to see which updates have been blocked before rebooting. If updates are blocked and then unblocked after reboot, there's something that's re-enabling them. This could be caused by your antivirus or security software. If nothing is blocked then there is something interfering with the script. This could also be caused by antivirus or security software, or it could be an issue with how Ancile hides updates.

Whatever the problem is, if it persists, you can send me a debug log by:

1) Delete any old Ancile log files 1) Open "config.ini" in any text editor 1) Change "DEBUG=N" to "DEBUG=Y" 1) Save and close "config.ini" 1) Run Ancile 1) PM me the log after Ancile has finished.

[–] [deleted] 0 points 2 points (+2|-0) ago 

[Deleted]

0
2

[–] Abym 0 points 2 points (+2|-0) ago 

Hi, I have a question maybe it's not the right place to do so, but i wanted to know when must i use Ancile for a new install of win7? should i run windows update once or something ? thanks for answering.

0
1

[–] matthewlinton [S] 0 points 1 points (+1|-0) ago 

On a new install of Windows I recommend running Windows Update at least once before running Ancile. This may install some unwanted updates, but Ancile will just uninstall them. The only reason I recommend that is because there are some issues with Windows Update that will cause Ancile to take a very long time to complete (until those specific issues are patched). By running Windows update at least once, there is less of a chance that you'll get stuck waiting hours for Ancile to finish. Another reason is that the Windows update program may not have completely initialized all of its update information after a fresh install. This means that you would have to run it before and then after anyway.

0
2

[–] klobos 0 points 2 points (+2|-0) ago 

Run it once and let windows install everything it wants? I stopped updating win 7 a while ago and even then selectively choose what I wanted and what I didn't.

Also, will this turn services on that I have already shut off?

What are the third party plugins?

0
2

[–] Abym 0 points 2 points (+2|-0) ago 

Thanks a lot for answering that fast ! I will. Thank you for sharing your work too. Gambatte, Bon Courage, Keep it up !

0
2

[–] santino 0 points 2 points (+2|-0) ago  (edited ago)

Nice! Thank you, Matthew.

I'm having trouble accessing Bitbucket download section for any project, but I'll try 1.10 ASAP.

edit: They're having some problems: https://status.bitbucket.org/

0
1

[–] matthewlinton [S] 0 points 1 points (+1|-0) ago 

You're welcome.

I ran into that issue today as well. It's always reassuring to know that it's not just you having problems :)

0
2

[–] Water 0 points 2 points (+2|-0) ago 

Keep up the great work for people stuck on Windows!

0
2

[–] matthewlinton [S] 0 points 2 points (+2|-0) ago 

I'll do my best. Thanks :)

0
1

[–] bl0ck0ut 0 points 1 points (+1|-0) ago  (edited ago)

'FATAL ERROR: USER DOES NOT HAVE ADMINISTRATIVE RIGHTS.' (Ancile 1.10)

Apparently I cannot get the latest version of ancile.cmd or/and any file is calling to gain administrative privileges. On line 7 on the log file after the Windows version in brackets, the following error is thrown: FATAL ERROR: User does not have Administrative rights.

What I've already tried:

  1. right-click on ancile.cmd file and "run as Administrator"
  2. open a Command Prompt with a right-click and "run as Administrator". Then type ./ancile.cmd
  3. run a PowerShell session as in (2)
  4. run (2) but typed: runas /user:<my_local_machine_name>\administrator "path\to\ancile.cmd" (*) with the error 1058: The service cannot be started, either because it is disabled or because it has no enabled devices associated with it.
  5. made a sudo.bat and run as admin with the line (all in the same dir as ancile.cmd): powershell.exe -Command "Start-Process ./ancile.cmd \"/k cd /d %cd%\" -Verb RunAs"
  6. escalate privileges in a batch file run as admin with: nircmd elevate ancile.cmd

Also made sure all the files in the Ancile folder where "Unblock", to no avail

(*) https://technet.microsoft.com/en-us/library/cc771525(v=ws.11).aspx

0 comments save edit delete

0
0

[–] matthewlinton [S] 0 points 0 points (+0|-0) ago 

Hmmm... I've seen a few people having permission issues with administrative rights both under command and power shells. Unfortunately I don't have any solid solutions yet.

A few things you could look into:

  • What security/antivirus software are you using? Some security software (rightfully) stops scripts from running as an Administrator no matter what.

  • Are you part of an Active Directory network (i.e. on your work computer)? Your SA could be disabling scripts that way.

  • Does your account actually have the ability to get Admin rights? It sounds like you know what you're doing, but it doesn't hurt to double check.

  • What locality is your version of Windows? I've developed Ancile under a US English version of Windows, and have slowly discovered that international versions of Windows behave unpredictably and there's no documentation to help figure out those quirks.

  • you can also run "lib/debuginfo.cmd" as an Administrator and review or PM me the log file. If you can't get that to run as an admin, you can try running it as a regular user.

  • Finally, you can add "CHECKADMIN=N" to "config.ini". This will disable the admin check in Ancile. You'll want to double check the log files to make sure that everything ran correctly.

Let me know how things turn out.

0
0

[–] bl0ck0ut 0 points 0 points (+0|-0) ago  (edited ago)

I strongly suspect you did a copy/paste of a command you didn't fully research and understand. We've all been there ;) That said I think you've done a great job with Ancile. Here's the fix.

We're going to use the terms 'admin privileges' and 'admin rights' as synonyms here, but we should keep in mind the difference between an admin account with admin rights and an elevated account, a.k.a. a non-admin account with admin privileges.

On line 80 of 'ancile.cmd' you invoke <net session> with:

net session >nul 2>&1

then redirecting the STDERR 2 to STDERR 1, executing the rest of the script only if the ERRORLEVEL is 0, i.e. no errors are thrown, or sending it to ERRORCHECK otherwise - lines 82-88.

net session standard errors handling is based on whether the Windows Service "Server" is running when the <net session> command is invoked, regardless of the privileges granted to the user executing it. Testing the command(1):

net session >nul & ECHO %ERRORLEVEL%

on an Administrator account in a Command Prompt with admin rights and without admin rights, leads to unpredictable STDERR results:

<----------------------------------------------> ADMINISTRATOR ACCOUNT
-\     |       with        |       with        |
-  \   | "Server" service  | "Server" service  |
-    \ |      running      |    not started    |
------------------------------------------------
with   |                   |                   |
admin  |         0         |         2         |
priv   |                   |                   |
------------------------------------------------
without|                   |                   |
admin  |         2         |         2         |
priv   |                   |                   |
------------------------------------------------

You can clearly see the issues. If the "Server" service has not been started, you're halting the execution of the script even if invoked as admin with admin rights - STDERR 2. Only while "Server" is running, the <net session> behaves as you may expect. I've done the same testing on an elevated account and not surprisingly, the results are identical.

 

The fix is quite straightforward: you need to check the "Server" service status before calling the <net session> command, and go from there. You could use net start(2), but I suggest using the sc query command, it looks more effective:

sc query LanmanServer | findstr "RUNNING" >nul
IF %ERRORLEVEL% NEQ 0 (
        ECHO PRIV CHECK FAIL: The LanmanServer service is not running. <net session> fails.>> "%LOGFILE%"
        whoami /all >> "%LOGFILE%" 2>&1
        ECHO FATAL ERROR: The Server service is not running. 
        ECHO              Run services.msc and start it manually. 
        ECHO              Then execute ancile.cmd again.
        ECHO.
        GOTO END
)

At this point we would want to start the "Server" service with <sc start>, but you need admin priv. I don't think that leaving the task to the user is such a bad idea anyway.
To be completely honest with you, after checking what debuginfo.cmd does, I had a laugh at your request to PM its log to you ;) You even traceroute back to Bitbucket... Should I start worrying? lol Thank you for all your efforts.

 

(1) You need to execute the command two times to get the current and correct STDERR showing when you run multiple commands on the same line as the STDERR is updated only at execution end!  

(2) net start | findstr /R /C:"< Server>" >nul 

Mind the <space> before the "S" of "Server" or you will match all the lines containing the word "Server" which are possibly more than one, e.g. DCOM Server Process Launcher, SQL Server VSS Writer, etc. This would work on any WINVER though.

 

 


Reference:

] "net session" manual ->{O} 

] "net helpmsg 2114 server service is not started" error ->{O} or {O} 

] "net session >nul 2>&1" explanation ->{O} 

] How to test whether a service is running from the command line ->{O} 

] FINDSTR manual ->{O} , {O} and {O} 

] SC command ->{O} and {O}

0
1

[–] Voatuser835 0 points 1 points (+1|-0) ago 

Thanks for this great work. Anyway i'm facing a little issue: after Ancile completed his process, i'm not able to check for updates anymore. I keep getting error code "8024402F". Any idea? Keep it up!

0
2

[–] matthewlinton [S] 0 points 2 points (+2|-0) ago 

This looks like a fairly common error that pops up on Windows 7 & 8 and can be caused by a number of things.

Unfortunately, my quick search didn't come up with one catch all solution. Hopefully one of these solutions will help you.

0
2

[–] Voatuser835 0 points 2 points (+2|-0) ago  (edited ago)

Well, i feel stupid now, but i didn't notice i had the option "Never check for updates" turned on. I changed it and now it works.

I have few question to ask if it not bother you: * Should i run Ancile every time windows install new updates? * Is it safe to install optional/recommended updates?

Thanks you very much again.