BatchPatch Forums Home › Forums › BatchPatch Support Forum › BatchPatch and computer hangsup
- This topic has 1 reply, 2 voices, and was last updated 8 years, 4 months ago by doug.
-
AuthorPosts
-
August 18, 2016 at 1:38 pm #9263StefanEParticipant
Hello,
I got an issue where BatchPatch slows down my computer and in the end everything hangs up and even the taskmanager can not be started. Reboot also fails most times. Then a hard reset of my machine is neccessary. I think I found the issue and I am not sure if this can be handled better by BatchPatch:
I have some terminal servers where the windows update services is disabled by default to prevent update messages to users. When I want to patch these servers I have to enable the service and start it. For enable I using remote command “sc config wuauserv start= auto”. By misstake I have used the command “sc config wuauserv start=auto” which is almost the same, only the blank after the = is missing. For the first servers I got a strange return code and the other never brought back any results, just that the command will be executed. After waiting a while BatchPatch doesn’t seem to do anything. When trying to close it I could not be close (even over Taskmanager). In the end also other programs on my computer hangs up or could not be started. Is it possible that this is caused by BatchPatch through any bug or memory leak whatever?
Stefan
August 18, 2016 at 4:39 pm #11360dougModeratorHi Stefan – What you’re describing doesn’t really sound like an issue with BatchPatch. It sounds like possibly there is something (or was something) going on with your computer/OS. However, it’s very difficult to say for sure. If you had noticed that the memory usage by BP was absurdly high in task manager, then that certainly might indicate a leak, but from what you described that doesn’t seem evident. BP has a small memory footprint, and we have not observed nor have any other customers reported any clear memory leaks.
The command “sc config wuauserv start=auto” should work just fine, even without the space after the = sign. I wonder if your computer had some kind of issue while you were using BatchPatch, and so it seemed like BatchPatch was the source of the problem when really BatchPatch freezing was just a symptom of a larger problem that was occurring on your machine. This would also explain why other applications froze.
-Doug
-
AuthorPosts
- You must be logged in to reply to this topic.