OK to install October updates?

On 10/28/2016 6:52 AM, burfordTjustice wrote:
On Thu, 27 Oct 2016 11:47:44 -0500
Jo-Anne wrote:

Microsoft's October rollup updates have been available for almost two
weeks, and a newsletter I subscribe to says they're OK to install
now. Has anyone had trouble with any of them?

Why do you subscribe to a newsletter you do not believe???


That's a silly question. The newsletter can describe only its editor's
own experiences and those of people who contact her. This forum is far
wider and with some very knowledgeable members, whose posts I take
seriously. If the newsletter says there's a problem with an update, I
don't install that update. In the past, if it said an update was OK, I
was comfortable installing it. Now, however, with all the updates lumped
together, I figure I need to be more careful.

--
Jo-Anne

On 10/27/2016 11:50 AM, Z. wrote:
Jo-Anne wrote:
Microsoft's October rollup updates have been available for almost two
weeks, and a newsletter I subscribe to says they're OK to install now.
Has anyone had trouble with any of them? The updates I'm being offered
are

KB3188740 for .NET Framework 3.5.1
KB3185330, the monthly "quality" rollup for W7 x64-based systems
KB890830, the monthly Malicious Software Removal Tool for W7 x64


I did it and then uninstalled KB3185330. Since then there is a Windows
log that CCleaner can't clean and one cannot open it to see what's being
logged from the Hosts file. Me no like.


Thank you, Z. Why did you uninstall the rollup update? Was it causing
problems?

--
Jo-Anne

On 10/27/2016 3:25 PM, VanguardLH wrote:
Jo-Anne wrote:

Microsoft's October rollup updates have been available for almost two
weeks, and a newsletter I subscribe to says they're OK to install
now. Has anyone had trouble with any of them? The updates I'm being
offered are

KB3188740 for .NET Framework 3.5.1
KB3185330, the monthly "quality" rollup for W7 x64-based systems
KB890830, the monthly Malicious Software Removal Tool for W7 x64

The one you do NOT want is:

October 2016 Preview of Monthly Quality Rollup for Windows 7 SP1 and
Windows Server 2008 R2 SP1
https://support.microsoft.com/en-us/kb/3192403

That is a *preview* of updates to be released NEXT month. Haven't a
clue why Microsoft is so obvious in using their customers as unpaid
voluntary beta testers. However, a lot of users never bother to review
or research an offered update and instead take everything shoved at
them. Hell, there are still lots of users that leave automatic updating
enabled for Windows Update so they don't know that the state of their
computer has been changed and then report "suddenly something happened
and I didn't change anything." Yes they did. They granted permission
for someone else to change their setup.

9 days ago I installed the 3 you mentioned. The MSRT never installs.
All it does is download, run, and delete itself if no malware was found
by it. I've not noticed any problems with my setup since then.

I have not enountered a problem using CCleaner after applying KB3185330
that Z mentioned. I was at version 5.22.5724. That ran fine after the
KB3185330 update. I just upgraded to 5.23.5808. That runs fine, too.
Don't know what Z was trying to say with "logged from the Hosts file".
That is a static file of hostname to IP address lookups, and it is not a
log file.


Thank you, Vanguard. I had already hidden the preview update. For now, I
think I'll install the .NET Framework update and the MSRT.

--
Jo-Anne

Jo-Anne wrote:
On 10/27/2016 11:50 AM, Z. wrote:
Jo-Anne wrote:
Microsoft's October rollup updates have been available for almost two
weeks, and a newsletter I subscribe to says they're OK to install now.
Has anyone had trouble with any of them? The updates I'm being offered
are

KB3188740 for .NET Framework 3.5.1
KB3185330, the monthly "quality" rollup for W7 x64-based systems
KB890830, the monthly Malicious Software Removal Tool for W7 x64


I did it and then uninstalled KB3185330. Since then there is a Windows
log that CCleaner can't clean and one cannot open it to see what's being
logged from the Hosts file. Me no like.


Thank you, Z. Why did you uninstall the rollup update? Was it causing
problems?


I'm not doing any more roll ups. I hear they spy on you.

--
Z.

On 10/27/2016 11:47 AM, Jo-Anne wrote:
Microsoft's October rollup updates have been available for almost two
weeks, and a newsletter I subscribe to says they're OK to install now.
Has anyone had trouble with any of them? The updates I'm being offered are

KB3188740 for .NET Framework 3.5.1
KB3185330, the monthly "quality" rollup for W7 x64-based systems
KB890830, the monthly Malicious Software Removal Tool for W7 x64



Thank you, everyone! For now I'm not going to install the monthly rollup
KB3185330.

Also, I just read in Ask Woody that one can get the rollup's security
updates without the nonsecurity updates by going through several steps
at the Microsoft website. The article about this is at
http://www.infoworld.com/article/313...-machines.html
in case anyone else is interested. It's a lot more work than using
Automatic Updates (which I have set for notification only), but in
theory it should enable us to avoid at least some of what we don't want.

--
Jo-Anne

Z. wrote:

VanguardLH wrote:

I couldn't quite figure out what Z was trying to say; however, as far as
CCleaner is concerned, I've had no problems with that program since
applying KB3185330. I also have not had the lockup programs reported in
the AskWoody article.

ANY update from Microsoft, anti-virus vendor, hardware driver, et cetera
can cause new problems. Backups are important.

The file that CCleaner can't delete is in
C;/User/Me/AppData/Local/Microsoft/Windows/WebCache and the file is
called V01.log. If I delete it manually or with CCleaner, it keeps
coming back. When I open it, there is a bunch of zeros, thousands of
them. It's size is 512KB.

I also have that file. CCleaner doesn't delete files that are in use.
If the file is locked, CCleaner (and most tools) cannot delete it. You
have to exit whatever process has a handle on that file. I use Unlocker
to check for ownership along with giving me the ability to delete locked
files (it tries to exit the owning process, and if that fails then it
will schedule a delete on Windows startup using a special registry entry
for that purpose).

Unlockers shows that v01.log is in use by the taskhost.exe process.
That is a Windows process. It is the parent process for methods
(functions) called out of DLLs that are Windows services. DLLs (Dynamic
Linked Libraries) are .dll file containing a slew of methods called by
programs although it can have a main() method that runs when the DLL is
loaded into memory. There may me multiple instances of taskhost.exe if
multiple unrelated services via DLL are started. For me and the current
taskhost.exe that is loaded, its parent process is services.exe. So
taskhost was loaded on behalf of the service controller to run a service
from a .dll file.

I could try to kill taskhost.exe to unlock the v01.log file but then I'd
probably screw up some service. I used SysInternal's Process Explorer
to look at the threads for taskhost.exe and saw it was accessing the
following DLLs:

ntdll.dll - core OS file,
https://en.wikipedia.org/wiki/Micros...iles#NTDLL.DLL
PlaySndSrv.dll - PlaySoundService, a Windows file
MsCtfMonitor.dll - text services (e.g., floating language bar)
WINMM.dll - Windows Multimedia API
ESENT.dll: Jet database,
https://en.wikipedia.org/wiki/Extensible_Storage_Engine
ole32.dll - https://en.wikipedia.org/wiki/Object..._and_Embedding
(renamed to ActiveX)

So the file reappears because something in Windows or IE uses it again
and has it in use (locked) so you cannot delete unless you try something
more robust than CCleaner - which means you had better know what you are
trying to delete.

If I wanted to better see what process was accessing that file, I'd use
a file monitor to catch for writes to the file. Since I'm not
interested in deleting a system file, I won't bother monitoring writes
to it. It probably gets [re]created so soon after Windows starts up
that monitoring for a create of the file would happen too late by the
time I got to load the file monitor.

My CCleaner does not puke on an error trying to delete anything under
the webcache folder. I have CCleaner configured with its default set of
choices of what to cleanup under both the Windows and Applications
categories. The only modifications I made to those was for Firefox and
Google (to have CCleaner cleanup what the purge-on-exit options in those
web browsers should already have cleaned up). Perhaps you checked some
additional location or you added the webcache folder to the custom list
under Options - Include.

VanguardLH wrote:
Z. wrote:

VanguardLH wrote:

I couldn't quite figure out what Z was trying to say; however, as far as
CCleaner is concerned, I've had no problems with that program since
applying KB3185330. I also have not had the lockup programs reported in
the AskWoody article.

ANY update from Microsoft, anti-virus vendor, hardware driver, et cetera
can cause new problems. Backups are important.

The file that CCleaner can't delete is in
C;/User/Me/AppData/Local/Microsoft/Windows/WebCache and the file is
called V01.log. If I delete it manually or with CCleaner, it keeps
coming back. When I open it, there is a bunch of zeros, thousands of
them. It's size is 512KB.

I also have that file. CCleaner doesn't delete files that are in use.
If the file is locked, CCleaner (and most tools) cannot delete it. You
have to exit whatever process has a handle on that file. I use Unlocker
to check for ownership along with giving me the ability to delete locked
files (it tries to exit the owning process, and if that fails then it
will schedule a delete on Windows startup using a special registry entry
for that purpose).

Unlockers shows that v01.log is in use by the taskhost.exe process.
That is a Windows process. It is the parent process for methods
(functions) called out of DLLs that are Windows services. DLLs (Dynamic
Linked Libraries) are .dll file containing a slew of methods called by
programs although it can have a main() method that runs when the DLL is
loaded into memory. There may me multiple instances of taskhost.exe if
multiple unrelated services via DLL are started. For me and the current
taskhost.exe that is loaded, its parent process is services.exe. So
taskhost was loaded on behalf of the service controller to run a service
from a .dll file.

I could try to kill taskhost.exe to unlock the v01.log file but then I'd
probably screw up some service. I used SysInternal's Process Explorer
to look at the threads for taskhost.exe and saw it was accessing the
following DLLs:

ntdll.dll - core OS file,
https://en.wikipedia.org/wiki/Micros...iles#NTDLL.DLL
PlaySndSrv.dll - PlaySoundService, a Windows file
MsCtfMonitor.dll - text services (e.g., floating language bar)
WINMM.dll - Windows Multimedia API
ESENT.dll: Jet database,
https://en.wikipedia.org/wiki/Extensible_Storage_Engine
ole32.dll - https://en.wikipedia.org/wiki/Object..._and_Embedding
(renamed to ActiveX)

So the file reappears because something in Windows or IE uses it again
and has it in use (locked) so you cannot delete unless you try something
more robust than CCleaner - which means you had better know what you are
trying to delete.

If I wanted to better see what process was accessing that file, I'd use
a file monitor to catch for writes to the file. Since I'm not
interested in deleting a system file, I won't bother monitoring writes
to it. It probably gets [re]created so soon after Windows starts up
that monitoring for a create of the file would happen too late by the
time I got to load the file monitor.

My CCleaner does not puke on an error trying to delete anything under
the webcache folder. I have CCleaner configured with its default set of
choices of what to cleanup under both the Windows and Applications
categories. The only modifications I made to those was for Firefox and
Google (to have CCleaner cleanup what the purge-on-exit options in those
web browsers should already have cleaned up). Perhaps you checked some
additional location or you added the webcache folder to the custom list
under Options - Include.


Nothing there. I'll just live with it as it isn't causing any problems.

--
Z.

On Fri, 28 Oct 2016 11:06:24 -0500
Jo-Anne wrote:

On 10/28/2016 6:52 AM, burfordTjustice wrote:
On Thu, 27 Oct 2016 11:47:44 -0500
Jo-Anne wrote:

Microsoft's October rollup updates have been available for almost
two weeks, and a newsletter I subscribe to says they're OK to
install now. Has anyone had trouble with any of them?

Why do you subscribe to a newsletter you do not believe???


That's a silly question. The newsletter can describe only its
editor's own experiences and those of people who contact her. This
forum is far wider and with some very knowledgeable members, whose
posts I take seriously. If the newsletter says there's a problem with
an update, I don't install that update. In the past, if it said an
update was OK, I was comfortable installing it. Now, however, with
all the updates lumped together, I figure I need to be more careful.


So you only trust the newsletter when it says there is a problem.

Very weird.