Knowledge base kb2538242 zip file#
Knowledge base kb2538242 update#
Knowledge base kb2538242 windows 10#
Knowledge base kb2538242 series#
Knowledge base kb2538242 windows#

Knowledge base kb2538242 series#

So if there is some sort of damage to my system (either caused by the series of events mentioned here, or a cause of them), I can revert to it. I have a system image backup of my system as it was when I first registered it after receiving the replacement computer.

Knowledge base kb2538242 zip file#

Here's an attachment of a ZIP file created by the Ten Forums BSOD Log Collection Utility, which should contain all of the relevant error files from the Event Viewer and possibly other relevant information as well: There are other error logs as well, but those are the only two that I could spot that seem to possibly be connected to this incident.

3:26:06 AM 'Session 'ReadyBoot' stopped due to the following error: 0xC0000188' I believe that the first error was from around the time that I turned the computer off after the Leawo installer freeze.

Knowledge base kb2538242 windows#

Could this 'Getting Windows Ready' message on my new computer have been a sign of Windows trying to fix some sort of damage or corruption that it found on my suystem? And why did it stay on that message screen for so long (possibly over an hour)?įurthermore, when I checked the Event Viewer, I noted some errors that may be related to this incident.

If it wasn't installing updates, then what was it doing? I seem to recall a previous computer (not the one that I sent away and had replaced) giving me a 'Getting Windows Ready' message when starting up after a crash. Don't Turn off Your Computer' message rather worrisome, as it's usually a message that shows up when installing updates.

Knowledge base kb2538242 update#

I checked the update history, and sure enough, no updates had been installed. I am still worried about this, as I don't know whether it actually finished restarting properly, or crashed somewhere along the line and started up afterward.

Knowledge base kb2538242 windows 10#

About half an hour later, I got up and checked the computer, to find that it had completed restarting, and was now on the Windows 10 Lock Screen. Finally, after about 30 to 45 minutes (this was about 3:00 AM), I got tired of waiting and decided to give up and go to bed, leaving the computer as-is. (Keep in mind that to the best of my knowledge, Windows had not downloaded any updates that it had not yet installed.) And it stayed like this for an interminable amount of time. But instead of restarting quickly, it gave the message 'Getting Windows Ready. I read somewhere that sometimes restarting the computer sets it straight. I googled the process, and what I read inclined me to believe that it had nothing to do with the Leawo installation (contrary to what I had previously assumed) and that sometimes the process gets stuck. However, when I looked at the task manager, 'Windows Modules Installer Worker' was again still there, and still using a significant amount of system resources. I then started the computer back up, ran the Leawo installer as an administrator, and successfully competed the installation. Finally, when I realized that it was going to stay stuck, I turned off the computer (Start Menu, Power, Shut Down). I let the computer sit like this for somewhere between half an hour and an hour. I checked the task manager, and a process called 'Windows Modules Installer Worker' was using up about 50% of my CPU and a lot of RAM. As I was installing one particular program (Leawo Blu-ray Player, to be precise), the installer stayed permanently stuck toward the end (during the extraction phase) and never finished. Last night, I stayed up late in order to get as much work done on it as possible. I've been working with the replacement, installing all of the programs that I need and otherwise customizing it to fit my needs.

After trying to troubleshoot it (with the help of the people at this forum), I finally gave up and sent it back for a replacement. I had a computer (a refurbished HP 6305 Pro) which kept having BSODs. I don't believe that I had a BSOD this time (as there seem to be no dump files), but it was an odd and worrying event, and there seem to be some associated error logs (which I have included in this post). I hope that this is the right place to post this.