B Barrymer Contributor Joined Aug 8, 2018 Posts 92 Jul 28, 2020 #1 I am running Win7 x64 on a Lenovo AIO computer. Everything works well, except that when the computer is in "Sleep" mode, it shuts down on its own. When I open the computer again, it tells me it shut down improperly. I updated the BIOS but the problem still persists. Also ran the Windows Update Forum Posting Instructions. The SFCFIX found one corruption and fixed it. Here is a link to the CBS files CBS.zip I'd appreciate your help with this perplexing issue.
I am running Win7 x64 on a Lenovo AIO computer. Everything works well, except that when the computer is in "Sleep" mode, it shuts down on its own. When I open the computer again, it tells me it shut down improperly. I updated the BIOS but the problem still persists. Also ran the Windows Update Forum Posting Instructions. The SFCFIX found one corruption and fixed it. Here is a link to the CBS files CBS.zip I'd appreciate your help with this perplexing issue.
B Barrymer Contributor Joined Aug 8, 2018 Posts 92 Jul 28, 2020 #2 If the link to the CBS files above doesn't work, please try this: CBS.zip
xrobwx71 Administrator Staff member Joined Sep 27, 2019 Posts 2,631 Location Panama City Beach, FL Jul 29, 2020 #3 @Barrymer Was sent here from this post: Computer Shuts Down Improperly During Sleep Mode
B Barrymer Contributor Joined Aug 8, 2018 Posts 92 Jul 29, 2020 #4 Another link for CBS files: CBS.zip This should work.
P PeterJ Moderator, Windows Update Expert, Security Analyst Staff member Joined Dec 14, 2014 Posts 12,633 Jul 29, 2020 #5 Hello and welcome, Step 1: Warning: This script was written specifically for this user, for use on that particular machine. Do not run this script on another machine. Download the Farbar Recovery Scan Tool and save it to your Desktop: 64-bit: Downloading Farbar Recovery Scan Tool Download the attachment fixlist.txt and save it to your desktop. Right-click on FRST64.exe and select "Run as administrator". Press the Fix button. The tool will now process fixlist.txt. If for some reason the tool needs a restart, please make sure you let the system restart normally. After that let the tool complete its run. When finished, a log called Fixlog.txt will appear in the same directory the tool is run from. Post the logfile Fixlog.txt as attachment in your next reply. Step 2: Follow the instructions below to run a scan with the System Update Readiness Tool (SURT) and provide a log. Download SURT for your system. (Windows 7 SP1 x64) Once downloaded, execute the installer, and go through the installation (this process can take around 15-20 minutes). On completion, a log will be created in C:\Windows\Logs\CBS\CheckSUR.log. Attach this log in your next reply. Alternatively, if these instructions are unclear for you, you can follow the tutorial below. System Update Readiness Tool (SURT) Attachments fixlist.txt 126.2 KB · Views: 3
Hello and welcome, Step 1: Warning: This script was written specifically for this user, for use on that particular machine. Do not run this script on another machine. Download the Farbar Recovery Scan Tool and save it to your Desktop: 64-bit: Downloading Farbar Recovery Scan Tool Download the attachment fixlist.txt and save it to your desktop. Right-click on FRST64.exe and select "Run as administrator". Press the Fix button. The tool will now process fixlist.txt. If for some reason the tool needs a restart, please make sure you let the system restart normally. After that let the tool complete its run. When finished, a log called Fixlog.txt will appear in the same directory the tool is run from. Post the logfile Fixlog.txt as attachment in your next reply. Step 2: Follow the instructions below to run a scan with the System Update Readiness Tool (SURT) and provide a log. Download SURT for your system. (Windows 7 SP1 x64) Once downloaded, execute the installer, and go through the installation (this process can take around 15-20 minutes). On completion, a log will be created in C:\Windows\Logs\CBS\CheckSUR.log. Attach this log in your next reply. Alternatively, if these instructions are unclear for you, you can follow the tutorial below. System Update Readiness Tool (SURT)
B Barrymer Contributor Joined Aug 8, 2018 Posts 92 Jul 29, 2020 #6 Hi Peter- I completed the steps you requested and attached below is the output. Thanks for your help with this perplexing issue. -Barry Attachments Fixlog.txt 63.7 KB · Views: 3 CheckSUR.persist.log 1.1 MB · Views: 3
Hi Peter- I completed the steps you requested and attached below is the output. Thanks for your help with this perplexing issue. -Barry
P PeterJ Moderator, Windows Update Expert, Security Analyst Staff member Joined Dec 14, 2014 Posts 12,633 Jul 30, 2020 #7 The problems with the registry keys were already detected almost 2 years ago. How long have you experienced the 'sleep' issue ? Step 1: Warning: This script was written specifically for this user, for use on that particular machine. Do not run this script on another machine. Download the attachment fixlist.txt and save it to your desktop. Right-click on FRST64.exe and select "Run as administrator". Press the Fix button. The tool will now process fixlist.txt. If for some reason the tool needs a restart, please make sure you let the system restart normally. After that let the tool complete its run. When finished, a log called Fixlog.txt will appear in the same directory the tool is run from. Post the logfile Fixlog.txt as attachment in your next reply. Step 2: Start the System Update Readiness Tool (SURT) again. On completion, attach the logfile C:\Windows\Logs\CBS\CheckSUR.log to your next reply. Attachments fixlist.txt 17.6 KB · Views: 5
The problems with the registry keys were already detected almost 2 years ago. How long have you experienced the 'sleep' issue ? Step 1: Warning: This script was written specifically for this user, for use on that particular machine. Do not run this script on another machine. Download the attachment fixlist.txt and save it to your desktop. Right-click on FRST64.exe and select "Run as administrator". Press the Fix button. The tool will now process fixlist.txt. If for some reason the tool needs a restart, please make sure you let the system restart normally. After that let the tool complete its run. When finished, a log called Fixlog.txt will appear in the same directory the tool is run from. Post the logfile Fixlog.txt as attachment in your next reply. Step 2: Start the System Update Readiness Tool (SURT) again. On completion, attach the logfile C:\Windows\Logs\CBS\CheckSUR.log to your next reply.
B Barrymer Contributor Joined Aug 8, 2018 Posts 92 Jul 30, 2020 #8 I don't think the "sleep" issue can have started more than about 5 weeks ago. (At first I thought it was just a freak thing. Then I tried some things myself to fix it. Then I called on you guys at the computer FBI. I redid the files as you requested and attached them below. I hope I got it right this time. Attachments Fixlog.txt 63.7 KB · Views: 2 CheckSUR.log 1.3 KB · Views: 2
I don't think the "sleep" issue can have started more than about 5 weeks ago. (At first I thought it was just a freak thing. Then I tried some things myself to fix it. Then I called on you guys at the computer FBI. I redid the files as you requested and attached them below. I hope I got it right this time.
P PeterJ Moderator, Windows Update Expert, Security Analyst Staff member Joined Dec 14, 2014 Posts 12,633 Jul 31, 2020 #9 It looks you ran the fixlist.txt from message #5 again. Perform the instructions in message #7 again.
It looks you ran the fixlist.txt from message #5 again. Perform the instructions in message #7 again.
B Barrymer Contributor Joined Aug 8, 2018 Posts 92 Jul 31, 2020 #10 I believe I did run the fixlist from message #7. The FRST program had asked me if I wanted to overwrite the earlier program and I said "Yes." Perhaps that is where the confusion arose. When I tried to do it again just now, after clicking on "Fix," it gave me a message it had already been done. It removed the fixlist file from my desktop and replaced it with the Fixedlog file. So it won't even let me run it again. I'll wait to hear back from you.
I believe I did run the fixlist from message #7. The FRST program had asked me if I wanted to overwrite the earlier program and I said "Yes." Perhaps that is where the confusion arose. When I tried to do it again just now, after clicking on "Fix," it gave me a message it had already been done. It removed the fixlist file from my desktop and replaced it with the Fixedlog file. So it won't even let me run it again. I'll wait to hear back from you.
P PeterJ Moderator, Windows Update Expert, Security Analyst Staff member Joined Dec 14, 2014 Posts 12,633 Aug 1, 2020 #11 Restart the computer. Download the attachment fixlist.txt in message #7 again and save it to your desktop. Right-click on FRST64.exe and select "Run as administrator". It may update itself first. When done it will restart and showing the text "The tool is ready to use." above the search input field. Press the Fix button. The tool will now process fixlist.txt. If for some reason the tool needs a restart, please make sure you let the system restart normally. After that let the tool complete its run. When finished, a log called Fixlog.txt will appear in the same directory the tool is run from. Post the logfile Fixlog.txt as attachment in your next reply.
Restart the computer. Download the attachment fixlist.txt in message #7 again and save it to your desktop. Right-click on FRST64.exe and select "Run as administrator". It may update itself first. When done it will restart and showing the text "The tool is ready to use." above the search input field. Press the Fix button. The tool will now process fixlist.txt. If for some reason the tool needs a restart, please make sure you let the system restart normally. After that let the tool complete its run. When finished, a log called Fixlog.txt will appear in the same directory the tool is run from. Post the logfile Fixlog.txt as attachment in your next reply.
B Barrymer Contributor Joined Aug 8, 2018 Posts 92 Aug 1, 2020 #12 I deleted the previous fixlog. I downloaded fixlist from message #7 and saved it to my desktop as you instructed. I right-clicked on FRST and selected "Run as administrator." It did not update itself. The text "The tool is ready to use was shown above the search input field. I pressed "Fix," and this is what came up after just a few seconds. Attached is the resulting Fixlog.txt document. I'll wait to hear from you. Attachments Fixlog.txt 18.1 KB · Views: 2
I deleted the previous fixlog. I downloaded fixlist from message #7 and saved it to my desktop as you instructed. I right-clicked on FRST and selected "Run as administrator." It did not update itself. The text "The tool is ready to use was shown above the search input field. I pressed "Fix," and this is what came up after just a few seconds. Attached is the resulting Fixlog.txt document. I'll wait to hear from you.
P PeterJ Moderator, Windows Update Expert, Security Analyst Staff member Joined Dec 14, 2014 Posts 12,633 Aug 1, 2020 #13 Looks good. Start the System Update Readiness Tool (SURT) again. On completion, attach the logfile C:\Windows\Logs\CBS\CheckSUR.log to your next reply.
Looks good. Start the System Update Readiness Tool (SURT) again. On completion, attach the logfile C:\Windows\Logs\CBS\CheckSUR.log to your next reply.
B Barrymer Contributor Joined Aug 8, 2018 Posts 92 Aug 1, 2020 #14 I ran the SURT again as you requested. It ran for a full 30 minutes this time! The CheckSUR.log file produced is attached below. Attachments CheckSUR.log 1.3 KB · Views: 3
I ran the SURT again as you requested. It ran for a full 30 minutes this time! The CheckSUR.log file produced is attached below.
P PeterJ Moderator, Windows Update Expert, Security Analyst Staff member Joined Dec 14, 2014 Posts 12,633 Aug 2, 2020 #15 Restart the computer. Check Windows Update and report the result. If it fails, attach the zipped cbs.log to your next reply.
Restart the computer. Check Windows Update and report the result. If it fails, attach the zipped cbs.log to your next reply.
B Barrymer Contributor Joined Aug 8, 2018 Posts 92 Aug 2, 2020 #16 I restarted the computer. I went to Windows Update, but I'm not sure I understand what to look for. Here is a screenshot of the recent history. Going back to 8/11/2018 when Sysnative fixed my issue with updates I followed their advice and only updated "important" ones. There was only one failed update since then which I just noticed now. As you know, support for Win7 ended on 1/14/2020. Word was at that time that MS wasn't going to continue security updates. So on 2/2/2020 I purchased an antivirus program from Kaspersky. Coincidentally(?), that was the day the update from MS failed. Of course MS has continued to provide security updates and I have continued to download them. However, my understanding is that since I am using a third party antivirus, that supercedes MS Defender and only comes into play if I drop the third party antivirus. (Sorry if this is TMI.) Please let me know what you want me to do going forward.
I restarted the computer. I went to Windows Update, but I'm not sure I understand what to look for. Here is a screenshot of the recent history. Going back to 8/11/2018 when Sysnative fixed my issue with updates I followed their advice and only updated "important" ones. There was only one failed update since then which I just noticed now. As you know, support for Win7 ended on 1/14/2020. Word was at that time that MS wasn't going to continue security updates. So on 2/2/2020 I purchased an antivirus program from Kaspersky. Coincidentally(?), that was the day the update from MS failed. Of course MS has continued to provide security updates and I have continued to download them. However, my understanding is that since I am using a third party antivirus, that supercedes MS Defender and only comes into play if I drop the third party antivirus. (Sorry if this is TMI.) Please let me know what you want me to do going forward.
P PeterJ Moderator, Windows Update Expert, Security Analyst Staff member Joined Dec 14, 2014 Posts 12,633 Aug 2, 2020 #17 Looking good. The failed update for Windows Defender can be ignored as the latest updates for Windows Defender are successfully installed. With "Security updates" are ment security updates for the OS only. They are not related to updates for Windows Defender. Now we're done with WU please tell me the status with the sleep issue.
Looking good. The failed update for Windows Defender can be ignored as the latest updates for Windows Defender are successfully installed. With "Security updates" are ment security updates for the OS only. They are not related to updates for Windows Defender. Now we're done with WU please tell me the status with the sleep issue.
B Barrymer Contributor Joined Aug 8, 2018 Posts 92 Aug 2, 2020 #18 Last night before I went to bed I changed the power settings to put the computer in "sleep" mode after 30 minutes. This morning I found the computer had shut down. So the issue doesn't seem to be resolved.
Last night before I went to bed I changed the power settings to put the computer in "sleep" mode after 30 minutes. This morning I found the computer had shut down. So the issue doesn't seem to be resolved.
P PeterJ Moderator, Windows Update Expert, Security Analyst Staff member Joined Dec 14, 2014 Posts 12,633 Aug 2, 2020 #19 Lets have a look at some settings. Warning: This script was written specifically for this user, for use on that particular machine. Do not run this script on another machine. Download the attachment fixlist.txt and save it to your desktop. Right-click on FRST64.exe and select "Run as administrator". Press the Fix button. The tool will now process fixlist.txt. If for some reason the tool needs a restart, please make sure you let the system restart normally. After that let the tool complete its run. When finished, a log called Fixlog.txt will appear in the same directory the tool is run from. Post the logfile Fixlog.txt as attachment in your next reply. Attachments fixlist.txt 243 bytes · Views: 6
Lets have a look at some settings. Warning: This script was written specifically for this user, for use on that particular machine. Do not run this script on another machine. Download the attachment fixlist.txt and save it to your desktop. Right-click on FRST64.exe and select "Run as administrator". Press the Fix button. The tool will now process fixlist.txt. If for some reason the tool needs a restart, please make sure you let the system restart normally. After that let the tool complete its run. When finished, a log called Fixlog.txt will appear in the same directory the tool is run from. Post the logfile Fixlog.txt as attachment in your next reply.
B Barrymer Contributor Joined Aug 8, 2018 Posts 92 Aug 2, 2020 #20 I followed your instructions. After just a few seconds I got a message that it had completed and the Fixlog could be found in the same directory as FRST. The Fixlog is attached below. Please let me know where to go from here. Attachments Fixlog.txt 4.4 KB · Views: 2
I followed your instructions. After just a few seconds I got a message that it had completed and the Fixlog could be found in the same directory as FRST. The Fixlog is attached below. Please let me know where to go from here.