W10
- Tetge
- Fourth Gear
- Posts: 2528
- Joined: Fri Sep 12, 2008 12:00 pm
Re: W10
Did you tell the tool to fix things or did you just run the first script and have it report? You need to let it fix the component store issue, which is the second script run with administrative privileges. Since I just fell off a turnip truck, I would not know what the errors identified meant even if I saw the log, so I would simply let the tool do its thing and see if that fixed the problem. If that fails, then you should completely format your drive, including wiping out the hidden partitions that W8.1 puts on the drive, and then do a clean install, backing things up to an exterior USB HD as you go along, using CloneZilla. This will make your computing future a lot easier.
-
- Second Gear
- Posts: 907
- Joined: Fri Mar 29, 2013 4:25 pm
Re: W10
I ran both scripts. For the /scanhealth, and then the /restorehealth. The message I posted is what I got after the restorehealth. I'm guessing it didn't work, and I'll end up having to do a clean install. Oh well.
- Tetge
- Fourth Gear
- Posts: 2528
- Joined: Fri Sep 12, 2008 12:00 pm
Re: W10
Perhaps you should try again and just run the command below, just to be sure since this should fix the updating issue. I assume that it took the 15 minutes or so and that you rebooted and tried a manual update? Perhaps you should post the contents of the log it created so we can have a look?
/RestoreHealth: This checks for component store corruption, records the corruption to C:\Windows\Logs\CBS\CBS.log and fixes the corruption using Windows Update or using your Windows installation source. This operation takes approximately 10-15 minutes or more depending on the level of corruption and the speed of your computer.
In short, the first two options just inform you about corruption, and only the last one does the actual repair. So, to fix the component store corruption, you need to do the following:
1.Open the command prompt as administrator (see all ways to open an elevated command prompt)
2.Type the following command: Dism /Online /Cleanup-Image /RestoreHealth
The /Online switch tells DISM to perform the repair on the currently booted OS.
/RestoreHealth: This checks for component store corruption, records the corruption to C:\Windows\Logs\CBS\CBS.log and fixes the corruption using Windows Update or using your Windows installation source. This operation takes approximately 10-15 minutes or more depending on the level of corruption and the speed of your computer.
In short, the first two options just inform you about corruption, and only the last one does the actual repair. So, to fix the component store corruption, you need to do the following:
1.Open the command prompt as administrator (see all ways to open an elevated command prompt)
2.Type the following command: Dism /Online /Cleanup-Image /RestoreHealth
The /Online switch tells DISM to perform the repair on the currently booted OS.
-
- Second Gear
- Posts: 907
- Joined: Fri Mar 29, 2013 4:25 pm
Re: W10
Here's the log:
[2396] Caller did not request sparse mount
[2396] Mounting new image.
Wim: [\\?\GLOBALROOT\device\harddisk0\partition1\Recovery\WindowsRE\Winre.wim]
Image Index: [1]
Mount Path: [C:\WINDOWS\TEMP\861c5a7e-eb97-47bd-bd9a-342dbd762691]
[2396] Wimserv process started for guid c7d5c4f3-4526-46d9-8ef9-c74cf4293a18. Id is 2456
[2456] ImageUnmarshallHandle: Reconstituting wim at \\?\GLOBALROOT\device\harddisk0\partition1\Recovery\WindowsRE\Winre.wim.
[2456] Mounted image at C:\WINDOWS\TEMP\861c5a7e-eb97-47bd-bd9a-342dbd762691.
[2396] [0x8007007b] FIOReadFileIntoBuffer:(1415): The filename, directory name, or volume label syntax is incorrect.
[2396] [0xc142011c] UnmarshallImageHandleFromDirectory:(511)
[2396] [0xc142011c] WIMGetMountedImageHandle:(2568)
[2396] [0x8007007b] FIOReadFileIntoBuffer:(1415): The filename, directory name, or volume label syntax is incorrect.
[2396] [0xc142011c] UnmarshallImageHandleFromDirectory:(511)
[2396] [0xc142011c] WIMGetMountedImageHandle:(2568)
[2396] ImageUnmarshallHandle: Reconstituting wim at \\?\GLOBALROOT\device\harddisk0\partition1\Recovery\WindowsRE\Winre.wim.
[2396] ImageUnmarshallHandle: Reconstituting wim at \\?\GLOBALROOT\device\harddisk0\partition1\Recovery\WindowsRE\Winre.wim.
[2396] ImageUnmarshallHandle: Reconstituting wim at \\?\GLOBALROOT\device\harddisk0\partition1\Recovery\WindowsRE\Winre.wim.
[2396] ImageUnmarshallHandle: Reconstituting wim at \\?\GLOBALROOT\device\harddisk0\partition1\Recovery\WindowsRE\Winre.wim.
[2396] ImageUnmarshallHandle: Reconstituting wim at \\?\GLOBALROOT\device\harddisk0\partition1\Recovery\WindowsRE\Winre.wim.
[2396] ImageUnmarshallHandle: Reconstituting wim at \\?\GLOBALROOT\device\harddisk0\partition1\Recovery\WindowsRE\Winre.wim.
[2396] ImageUnmarshallHandle: Reconstituting wim at \\?\GLOBALROOT\device\harddisk0\partition1\Recovery\WindowsRE\Winre.wim.
[2456] Received unmount request for image with guid c7d5c4f3-4526-46d9-8ef9-c74cf4293a18.
[2456] Unmount for image at C:\WINDOWS\TEMP\861c5a7e-eb97-47bd-bd9a-342dbd762691 complete.
After this, there were a WHOLE LOT of Chinese(?) characters.
[2396] Caller did not request sparse mount
[2396] Mounting new image.
Wim: [\\?\GLOBALROOT\device\harddisk0\partition1\Recovery\WindowsRE\Winre.wim]
Image Index: [1]
Mount Path: [C:\WINDOWS\TEMP\861c5a7e-eb97-47bd-bd9a-342dbd762691]
[2396] Wimserv process started for guid c7d5c4f3-4526-46d9-8ef9-c74cf4293a18. Id is 2456
[2456] ImageUnmarshallHandle: Reconstituting wim at \\?\GLOBALROOT\device\harddisk0\partition1\Recovery\WindowsRE\Winre.wim.
[2456] Mounted image at C:\WINDOWS\TEMP\861c5a7e-eb97-47bd-bd9a-342dbd762691.
[2396] [0x8007007b] FIOReadFileIntoBuffer:(1415): The filename, directory name, or volume label syntax is incorrect.
[2396] [0xc142011c] UnmarshallImageHandleFromDirectory:(511)
[2396] [0xc142011c] WIMGetMountedImageHandle:(2568)
[2396] [0x8007007b] FIOReadFileIntoBuffer:(1415): The filename, directory name, or volume label syntax is incorrect.
[2396] [0xc142011c] UnmarshallImageHandleFromDirectory:(511)
[2396] [0xc142011c] WIMGetMountedImageHandle:(2568)
[2396] ImageUnmarshallHandle: Reconstituting wim at \\?\GLOBALROOT\device\harddisk0\partition1\Recovery\WindowsRE\Winre.wim.
[2396] ImageUnmarshallHandle: Reconstituting wim at \\?\GLOBALROOT\device\harddisk0\partition1\Recovery\WindowsRE\Winre.wim.
[2396] ImageUnmarshallHandle: Reconstituting wim at \\?\GLOBALROOT\device\harddisk0\partition1\Recovery\WindowsRE\Winre.wim.
[2396] ImageUnmarshallHandle: Reconstituting wim at \\?\GLOBALROOT\device\harddisk0\partition1\Recovery\WindowsRE\Winre.wim.
[2396] ImageUnmarshallHandle: Reconstituting wim at \\?\GLOBALROOT\device\harddisk0\partition1\Recovery\WindowsRE\Winre.wim.
[2396] ImageUnmarshallHandle: Reconstituting wim at \\?\GLOBALROOT\device\harddisk0\partition1\Recovery\WindowsRE\Winre.wim.
[2396] ImageUnmarshallHandle: Reconstituting wim at \\?\GLOBALROOT\device\harddisk0\partition1\Recovery\WindowsRE\Winre.wim.
[2456] Received unmount request for image with guid c7d5c4f3-4526-46d9-8ef9-c74cf4293a18.
[2456] Unmount for image at C:\WINDOWS\TEMP\861c5a7e-eb97-47bd-bd9a-342dbd762691 complete.
After this, there were a WHOLE LOT of Chinese(?) characters.
- Tetge
- Fourth Gear
- Posts: 2528
- Joined: Fri Sep 12, 2008 12:00 pm
Re: W10
It appears that the system did fix some stuff. But, you are saying that the Windows Update still doesn't work. So, unless there is some firewall or anti virus blocking things or, unless that root kit that you got using file sharing has disabled your computer, it appears that you should completely wipe and format your entire drive, including those hidden partitions, and do a fresh install. This really is not all that bad as I assume that you have a nice big exterior HD that you can save all your data to. If you don't have one, you should get one as they are not super expensive and having a place to put copies of stuff and to make backups to is a basic requirement if you want to have a painless computing experience. My external USB 3.0 3TB HD is fast enough so that, although it is no SSD, it lets me transfer stuff to it as a backup library at a reasonable rate.
-
- Second Gear
- Posts: 907
- Joined: Fri Mar 29, 2013 4:25 pm
Re: W10
I ended up doing a fresh install. I backed up my emails, which was the most important thing. That worked. I reinstalled all my key programs, and am now waiting on a big update. It's installing 97 updates. Hopefully, they'll all be successful.
-
- Second Gear
- Posts: 907
- Joined: Fri Mar 29, 2013 4:25 pm
Re: W10
Everything seems to be going well, so far. Some updates failed last night. I did a restart and update this morning, and it hung up for a couple hours, but I just did a hard reset, and restarted the process. I think almost all of those updates were successful. We'll see if I end up with the same annoying cycle or not. Either way, I have already installed all the programs I need to run, so I probably won't mess with it again until I upgrade to the final release of W10, which will be free, so that's good.
Thanks for all the help, Pat.
Thanks for all the help, Pat.
- Tetge
- Fourth Gear
- Posts: 2528
- Joined: Fri Sep 12, 2008 12:00 pm
Re: W10
There is nothing to thank me for, unless something I posted actually turned out to be useful. But, I still maintain that you should get the latest 64 bit friendly CloneZilla and put it on a USB stick. or, if money is a serious issue, on a CD or DVD, and make a backup image of your complete HD with you system all updated and working well. Great insurance and very quick to restore.SonicVenum wrote:Everything seems to be going well, so far. Some updates failed last night. I did a restart and update this morning, and it hung up for a couple hours, but I just did a hard reset, and restarted the process. I think almost all of those updates were successful. We'll see if I end up with the same annoying cycle or not. Either way, I have already installed all the programs I need to run, so I probably won't mess with it again until I upgrade to the final release of W10, which will be free, so that's good.
Thanks for all the help, Pat.
-
- Second Gear
- Posts: 907
- Joined: Fri Mar 29, 2013 4:25 pm
Re: W10
You, at the very least, attempted to provide assistance. That's something worth giving thanks for in my book.
I'll do that. It's a good idea, especially with what it takes to get a system configured just so. Costco has a 3-pack for 16GB SanDisk thumb drives for $25. That's a pretty good deal. I'll jump on that. I also have a 1TB HDD as a part of my system, and I'm only using half of that, so there's plenty of room for backups.
I'll do that. It's a good idea, especially with what it takes to get a system configured just so. Costco has a 3-pack for 16GB SanDisk thumb drives for $25. That's a pretty good deal. I'll jump on that. I also have a 1TB HDD as a part of my system, and I'm only using half of that, so there's plenty of room for backups.