BrianDrab Emeritus Joined Oct 20, 2014 Posts 18,131 Location United States Apr 12, 2017 #81 Good. Now do the following. Step#1 - DISM /RestoreHealth Scan Warning:this fix is specific to the user in this thread. No one else should follow these instructions as it may cause more harm than good. If you are after assistance, please start a thread of your own. Right-click on the Start button and select Command Prompt (Admin) When command prompt opens, Copy (Ctrl+C) and Paste (Right-click > Paste) the following command into it, then press Enter Dism /Online /Cleanup-Image /RestoreHealth Once it finishes, copy and paste the following into the command-prompt window and press Enter. If prompted to overwrite the existing file go ahead. copy %windir%\logs\cbs\cbs.log "%userprofile%\Desktop\cbs.txt" Once this has completed please go to your Desktop and you will find CBS.txt => Please zip/upload to this thread. Please Note:: if the file is too big (over 7MB) to upload to your next post, please upload via a service such as Dropbox or One Drive or SendSpace and just provide the link.
Good. Now do the following. Step#1 - DISM /RestoreHealth Scan Warning:this fix is specific to the user in this thread. No one else should follow these instructions as it may cause more harm than good. If you are after assistance, please start a thread of your own. Right-click on the Start button and select Command Prompt (Admin) When command prompt opens, Copy (Ctrl+C) and Paste (Right-click > Paste) the following command into it, then press Enter Dism /Online /Cleanup-Image /RestoreHealth Once it finishes, copy and paste the following into the command-prompt window and press Enter. If prompted to overwrite the existing file go ahead. copy %windir%\logs\cbs\cbs.log "%userprofile%\Desktop\cbs.txt" Once this has completed please go to your Desktop and you will find CBS.txt => Please zip/upload to this thread. Please Note:: if the file is too big (over 7MB) to upload to your next post, please upload via a service such as Dropbox or One Drive or SendSpace and just provide the link.
D Dave S Contributor Joined Mar 21, 2016 Posts 345 Location Weston.Massachusetts Apr 12, 2017 #82 https://1drv.ms/u/s!AlcpvQccsoNmgUFQbsAuH3Q7VT1G Same old 1812 error on initialization good luck again; We can't get dism to run properly it would appear
https://1drv.ms/u/s!AlcpvQccsoNmgUFQbsAuH3Q7VT1G Same old 1812 error on initialization good luck again; We can't get dism to run properly it would appear
D Dave S Contributor Joined Mar 21, 2016 Posts 345 Location Weston.Massachusetts Apr 12, 2017 #83 I am running an errand for about a half hour
BrianDrab Emeritus Joined Oct 20, 2014 Posts 18,131 Location United States Apr 12, 2017 #84 You provided a link to the same file as last run. It's not current.
D Dave S Contributor Joined Mar 21, 2016 Posts 345 Location Weston.Massachusetts Apr 12, 2017 #85 I will redo and resend a new one
D Dave S Contributor Joined Mar 21, 2016 Posts 345 Location Weston.Massachusetts Apr 12, 2017 #86 https://1drv.ms/u/s!AlcpvQccsoNmgUJk4yGF3VxVXGGl
BrianDrab Emeritus Joined Oct 20, 2014 Posts 18,131 Location United States Apr 12, 2017 #87 The link is still pointing to an old file.
D Dave S Contributor Joined Mar 21, 2016 Posts 345 Location Weston.Massachusetts Apr 12, 2017 #88 https://1drv.ms/u/s!AlcpvQccsoNmgUJk4yGF3VxVXGGl
BrianDrab Emeritus Joined Oct 20, 2014 Posts 18,131 Location United States Apr 12, 2017 #89 That link doesn't go anywhere. Onedrive says it's unavailable.
D Dave S Contributor Joined Mar 21, 2016 Posts 345 Location Weston.Massachusetts Apr 12, 2017 #90 let me try again. I am obviously doing something wrong
D Dave S Contributor Joined Mar 21, 2016 Posts 345 Location Weston.Massachusetts Apr 12, 2017 #91 https://1drv.ms/u/s!AlcpvQccsoNmgUQitZrZhxfKR0Zv this looks better, I think. please let me know before you analyze
https://1drv.ms/u/s!AlcpvQccsoNmgUQitZrZhxfKR0Zv this looks better, I think. please let me know before you analyze
BrianDrab Emeritus Joined Oct 20, 2014 Posts 18,131 Location United States Apr 12, 2017 #92 The link works but the file is old. After running the dism command you may want to simply browse to c:\windows\logs\cbs and then right-click on the cbs.log file and then right-click on your desktop and paste it. Then just zip up and attach the cbs.log file from the desktop.
The link works but the file is old. After running the dism command you may want to simply browse to c:\windows\logs\cbs and then right-click on the cbs.log file and then right-click on your desktop and paste it. Then just zip up and attach the cbs.log file from the desktop.
D Dave S Contributor Joined Mar 21, 2016 Posts 345 Location Weston.Massachusetts Apr 12, 2017 #93 https://1drv.ms/u/s!AlcpvQccsoNmgUa0jsTfxJYJIWel is this better?
BrianDrab Emeritus Joined Oct 20, 2014 Posts 18,131 Location United States Apr 12, 2017 #94 Still old.
D Dave S Contributor Joined Mar 21, 2016 Posts 345 Location Weston.Massachusetts Apr 12, 2017 #95 It is the log directly from windows just after I ran the dism command. When I open it I see entries from 4/12/2017 after 2:00 They ar towards the bottom but I see them. isn't this the right data?
It is the log directly from windows just after I ran the dism command. When I open it I see entries from 4/12/2017 after 2:00 They ar towards the bottom but I see them. isn't this the right data?
BrianDrab Emeritus Joined Oct 20, 2014 Posts 18,131 Location United States Apr 12, 2017 #96 The last entry in the log I see is the following. Code: 2017-04-12 05:22:54, Info CBS Signalling IdleScavenge Complete. Is that what you see?
The last entry in the log I see is the following. Code: 2017-04-12 05:22:54, Info CBS Signalling IdleScavenge Complete. Is that what you see?
D Dave S Contributor Joined Mar 21, 2016 Posts 345 Location Weston.Massachusetts Apr 12, 2017 #97 I just ran the dism command again. got the same error 1812 and looked at tye log file it is bigger than the one I sent you. A lot of the same stuff is in there. The top of the list has a 4/11 date and lower there are 4/12 dates. Can I rename the file cbsold.log and then rerun?
I just ran the dism command again. got the same error 1812 and looked at tye log file it is bigger than the one I sent you. A lot of the same stuff is in there. The top of the list has a 4/11 date and lower there are 4/12 dates. Can I rename the file cbsold.log and then rerun?
BrianDrab Emeritus Joined Oct 20, 2014 Posts 18,131 Location United States Apr 12, 2017 #98 What's the last line in the log look like?
D Dave S Contributor Joined Mar 21, 2016 Posts 345 Location Weston.Massachusetts Apr 12, 2017 #99 2017-04-12 05:22:54, Info CBS Signalling IdleScavenge Complete. but there may be more to the right
BrianDrab Emeritus Joined Oct 20, 2014 Posts 18,131 Location United States Apr 12, 2017 #100 That matches exactly what was sent previously (see Post#96) above. Something must be up. Please do the following. FRST Fix NOTICE: This script was written specifically for this user, for use on that particular machine. Running this on another machine may cause damage to your operating system 1. Please download Farbar Recovery Scan Tool and save it to your Desktop. Note: You need to run the 64-bit Version so please ensure you download that one. 2. Download attached file and save it to the Desktop. Note. It's important that both files, FRST64 and fixlist.txt are in the same location or the fix will not work (in this case...the desktop). 3. Run FRST64 by Right-Clicking on the file and choosing Run as administrator. 4. Press the Fix button just once and wait. 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. 5. When finished FRST64 will generate a log on the Desktop (Fixlog.txt). Please post the contents of it in your reply. Attachments fixlist.txt 27 bytes · Views: 1
That matches exactly what was sent previously (see Post#96) above. Something must be up. Please do the following. FRST Fix NOTICE: This script was written specifically for this user, for use on that particular machine. Running this on another machine may cause damage to your operating system 1. Please download Farbar Recovery Scan Tool and save it to your Desktop. Note: You need to run the 64-bit Version so please ensure you download that one. 2. Download attached file and save it to the Desktop. Note. It's important that both files, FRST64 and fixlist.txt are in the same location or the fix will not work (in this case...the desktop). 3. Run FRST64 by Right-Clicking on the file and choosing Run as administrator. 4. Press the Fix button just once and wait. 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. 5. When finished FRST64 will generate a log on the Desktop (Fixlog.txt). Please post the contents of it in your reply.