-
Notifications
You must be signed in to change notification settings - Fork 0
[BUG-11845] Viewer version 4.0.4.314426 fails to install on Windows 10 #1964
Comments
Kyle Linden commented at 2016-04-27T19:17:39Z Hi StarWolff2000, You are using a Second Life Release Candidate viewer that was selected for you. You may be encountering a bug in that viewer. It is not unheard of for there to be stuck processes from the prior instance of Second Life running that prevent installing a new version. Win_crash_logger.exe is one of the common culprits here. Please right click on your windows task bar at the bottom of your screen and click Start Task Manager. Do you see any of the following still running when you believe you have quit Second Life?
If you do, select the process and click the End Process button. Now you should be able to install any of the viewers from the Alternate Viewers download page http://wiki.secondlife.com/wiki/Linden_Lab_Official:Alternate_Viewers or the current release from http://secondlife.com/support/downloads/. Please let us know if this helped at all and press the Info Provided button. Thanks! |
StarWolff2000 commented at 2016-04-28T07:43:49Z, updated at 2016-04-28T07:46:53Z ===SOLVED=== Thank you for reply, Kyle Linden Steps I took BEFORE I found the solution: 1st I re-downloaded the 4.0.4.314426, and attempted to install - still errors.
|
Kyle Linden commented at 2016-04-28T18:47:22Z, updated at 2016-04-28T18:48:03Z Hi StarWolff2000, That's a very interesting solution you worked out and definitely something we need to investigate further. Now that you can login will you please add the Help > About Second Life information to the environment field. This information will help us to reproduce the situation in which you encountered the install problems. Please press the Info Provided button when you update. Thanks! |
StarWolff2000 commented at 2016-04-29T13:25:18Z Hey Hy, Kyle Linden No, I'm not using Unicode in either my Windows Username nor SL username And yes, correction: I started with Viewer build 4.0.3.312816 (current release viewer) from the Downloads page Then SL auto-downloaded Viewer version 4.0.4.314426, and I got the errors It is possible the issue might be because I did not kill win_crash_logger.exe, (not recognizing it as an SL process until I mucked around in the SecondLifeViewer folder), when I first started encountering the errors. [suggestion: rename it to SL_crash_logger.exe] ABOUT Second Life: Second Life 4.0.4.314426 (Second Life Release) You are at 201.3, 250.7, 24.6 in Baku located at sim10295.agni.lindenlab.com (216.82.50.17:13007) CPU: AMD A4-5000 APU with Radeon(TM) HD Graphics (1499.98 MHz) Windows Graphics Driver Version: 8.17.0010.1452 J2C Decoder Version: KDU v7.2 Packets Lost: 27/4,411 (0.6%) |
Kyle Linden commented at 2016-05-02T17:10:50Z Hi StarWolff2000, Thank you for the update. Given this information it does seem like a duplicate of BUG-7873. We'll do additional testing on our side to rule out any Win10 install issues. Thank you |
Steps to Reproduce
Upon restarting the SL viewer, the viewer install proceeded. Near the end, I received 10 Error messages, it was unable to install: winmm.ddl - win_crash_logger.exe - ssleay32.dll - msvcr120.dll - msvcp120.dll - libhunspell.dll - libeay32.dll - glod.dll - fmodex.dll - SecondLifeViewer.exe - each with the message: "Error opening or writing the file: [SEE attached image for an example]. For each one, I tried 'Retry', with a repeat of the Error, then clicked 'Ignore'.
I closed all SL windows, and downloaded Viewer version 4.0.3.312826 from the Alternative Viewers page, and went to install it. I received the same 10 Error messages.
Actual Behavior
I was running Viewer version 4.0.3.312826 on Windows 10
SL auto-downloaded Viewer version 4.0.4.314426, and attempted to install on the next restart.
Expected Behavior
Expected it to install without Errors/Error messages. - especially a second attempt direct download.
Other information
Attachments
Links
Duplicates
Original Jira Fields
The text was updated successfully, but these errors were encountered: