Whirly Fizzle commented at 2014-11-23T08:39:06Z

This problem comes up a lot on the forums.

Just a couple of examples...

• http://community.secondlife.com/t5/Technical/I-m-told-I-ve-encountered-an-error-when-I-attempt-to-update-the/qaq-p/2793558
• http://community.secondlife.com/t5/Viewers/C-Program-Files-x86-SecondLifeViewer-win-crash-logger/qaq-p/2798654

It doesnt only happen to people updating through the automatic update (though this seems the most common trigger), it also happens when people try to update with a fresh download from https://secondlife.com/support/downloads/

I suspect the problem is caused by win_crash_logger not closing when the viewer is quit. I have seen a fair few people with extra stray win_crash_logger processes left running when logged out of all SL viewers.
The worst case I saw had 32 win_crash_logger processes left running :D

Chimera Firecaster commented at 2014-11-25T18:18:52Z

Alexa, I see you've entered "Needs More Info" to my Bug Report. Tell me what info you need and I'll provide it.

Whirly Fizzle commented at 2014-11-26T04:25:13Z

@chimera
If you think you have provided all the necessary information, you can click the "Info Provided" button at the top of this issue.

One thing I would check is, when you logout of the viewer, is there still a win_crash_logger process left running in windows task manager -> processes?

I was looking where the viewer installer wrote the log files to, but I cant find it. The installer log for a failed install would probably be the best information to provide.

Chimera Firecaster commented at 2014-11-26T22:31:08Z

All information has been provided

Gracie Goldflake commented at 2014-12-02T18:45:02Z

Ditto on everything Chimera has said.

I do not allow the download while I am inworld, but accept the forced download the next time I log in. That is when it happens.

Whirly, no win_crash_logger shows on my processes tab for any user.

BTW, this has been going on for over a year. I did not keep track of when it started. Assumed it would be fixed. But it happens every time.

Whirly Fizzle commented at 2015-01-22T18:10:42Z

I just had this problem for the first time. In my case the cause turned out to be Avast antivirus was scanning win_crash_logger.exe during the install, which caused the install to fail.
My Avast antivirus on this system is the standard Avast 2015 free version and it is running on default settings.
I was manually installing the windows build of http://automated-builds-secondlife-com.s3.amazonaws.com/hg/repo/sl-92_sl-92/rev/298129/index.html when it happened.
I don't usually use Avast antivirus, I just changed over to it from AVG so I do not know yet if this will be a common problem with Avast 2015.
Running the installer for a second time installed the viewer without any problems.

Chimera Firecaster commented at 2015-02-24T16:30:46Z

Just a note that the "Error Opening File for Writing: win_crash_logger.exe" bug reported 3 months ago continues to trigger when trying to do an install.

Chimera Firecaster commented at 2015-09-03T16:16:47Z

The bug "Error Opening File for Writing: win_crash_logger.exe" reported 10 months ago continues to trigger when doing an install.

Nicky Perian commented at 2016-04-04T03:18:03Z

I recently had this come up while testing auto update on Windows. My thinking (a SWAG) is that this is a timing issue related to the downloaded installer running from / called from a batch file, as I have never experienced the error when running the install with a mouse click from the manually downloaded location. I found that a selected Retry within the OS alarm message box would allow the files to install.