As I learned the official Windows Update service service must be at least available ("manual") but not "disabled" in order to be able to apply patches from Autopatcher.
As I found out the name of this service is different in WinXP ("Automatic updates") vs Win7 ("Windows Update").
Is this correct?
Furthermore I detected that the WinXP service "Automatic service" is NOT set back to "manual" by Autopatcher after application of updates. Instead it is automatically "started" from this moment. Is this intended?
Is there really no option in Autopatcher: "Put Automatic updates" back to "manual" ?
This should be changed in the next release of Autopatcher!
Peter
1
Different names for update service in WinXP and Win7?
Started by pstein, Dec 26 2010 12:08 PM
2 replies to this topic
#2
-
- Veterans
-
- 1,460 posts
audi 5k
- Gender:Male
Posted 26 December 2010 - 04:31 PM
I can't speak about how Windows 7 functions with regard to Automatic Updates (the service) but I know this - it can be disabled and will stay disabled when using AutoPatcher - AutoPatcher doesn't mess with this service. I have had Automatic Updates disabled for a long time on both 2000 and XP and I have never seen the service turn back on.
Now, what may be happening is Windows Update (needs the service running) or one of the updates you've installed has started (or set to automatic) this service - this sounds right and is the behavior of nearly everything we install or update anymore on our systems. I go through this with many applications, I have set some service to disabled (usually an auto-update feature) and sure enough, after the next update the service is set back to 'automatic'.
Bottom line - if you use Windows Update you want the service running (automatic), and AutoPatcher wont interfere with these settings. I'm not sure if WU/MU still functions with the service set to 'manual'? I guess from your experience you've set Automatic Update to 'manual' but it keeps getting set to 'automatic' - then I guess the answer is you need to leave it set to automatic or stop using WU/MU.
Now, what may be happening is Windows Update (needs the service running) or one of the updates you've installed has started (or set to automatic) this service - this sounds right and is the behavior of nearly everything we install or update anymore on our systems. I go through this with many applications, I have set some service to disabled (usually an auto-update feature) and sure enough, after the next update the service is set back to 'automatic'.
Bottom line - if you use Windows Update you want the service running (automatic), and AutoPatcher wont interfere with these settings. I'm not sure if WU/MU still functions with the service set to 'manual'? I guess from your experience you've set Automatic Update to 'manual' but it keeps getting set to 'automatic' - then I guess the answer is you need to leave it set to automatic or stop using WU/MU.
#3
-
- Veterans
-
- 3,851 posts
Super Helpful Guy
- Gender:Male
- Location:Brazil (Santa Maria - RS)
Posted 26 December 2010 - 07:24 PM
> This should be changed in the next release of Autopatcher!
if this was intended, for sure. but as mike stated, we don't mess with that service. i do know that there's something related to windows update service and windows seven, but it was done like that by ms, not us. some issues that i know that can happen due windows update disabled under seven are error codes 80070422, 80244019 and or 8DDD0018
[]s
if this was intended, for sure. but as mike stated, we don't mess with that service. i do know that there's something related to windows update service and windows seven, but it was done like that by ms, not us. some issues that i know that can happen due windows update disabled under seven are error codes 80070422, 80244019 and or 8DDD0018
[]s
1 user(s) are reading this topic
0 members, 1 guests, 0 anonymous users
