Windows 10: Annoying problem forcing me to format

For the past couple of months my computer has been frequently disconnecting. It seems to happen mostly in the morning but can happen at various times of the day. These disconnections typically last a second or two. But sometimes I have to replug the powerline adaptor.

I am connected via a Powerline 1200 and ethernet cat 6a cable and its cat 6a all the way to the router.

There is nothing showing in event viewer to indicate a cause.

When I perform sfc /scannow it reports corrupted files but dism is unable to repair them.

I think it is this corruption that is causing the computer to disconnect.

I am therefor thinking about formatting tomorrow morning.

Is there a tool that can verify the downloaded file's integrity (sha1 or something?) then I know the file is ok to use.

Also are there any iso's of the latest version of Windows 10?

I had hoped to stick with this problem until 16th July when Anniversary update would have been released but Microsoft have forced my hand as I use this computer for work and these disconnections I can do with without.

:)

 

E72 Focus Flash

Got this problem too!! It's ultimately annoying that it can't be forced off.

 

Freezing and buzzing sound Windows 10

I have a windows 10 tablet/ hybrid and sometimes the screen randomly freezes and there is an annoying buzzing sound which forces me to do a hard restart. I tried reinstalling Windows ten, updating drivers and many other thing but it still did not solve
this problem. I searched online and many other people had the same problem but with no solution. I think this is a problem only for windows 10 because it has never happened before on any other windows. Can someone please help me fix this problem because it
is getting really annoying especially when I'm in the middle of important work and am forced to do a hard restart.

Thanks in advance for any help.

 

I have made an ISO using Media Creation Tool, I just need to find published hash sums of it to compare with mine.

EDIT: I've read that MCT checks the integrity of the ISO download for you.

 

I've made two or three ISO's now and haven't checked them (as I never did get the hang of that) and they've all been fine! Last time I was getting errors that couldn't be fixed with scannow it was the drive that was failing. If you're going to do a clean install, then maybe it's time for a new hard drive as well?

 

I shall run the sfc command first thing after install.

 

Here's what I would do:

• If sfc keeps failing. You need to run DISM first: dism /online /cleanup-image /restorehealth
  to make sure it passes then run sfc /scannow. You may have to run sfc multiple times until it's clean
• Check if the powerline devices are connected on the outlet that has the same circuit breaker on both end.
  For testing purpose, try to connect the PC directly to the router to make sure it's not the powerline that causes disconnection.

 

This is the problem I had before. I am now on a freshly formatted Windows 10 with nothing else installed and I get this:

C:\Windows\system32>sfc /scannow

Beginning system scan. This process will take some time.

Beginning verification phase of system scan.
Verification 100% complete.

Windows Resource Protection found corrupt files but was unable to fix some
of them. Details are included in the CBS.Log windir\Logs\CBS\CBS.log. For
example C:\Windows\Logs\CBS\CBS.log. Note that logging is currently not
supported in offline servicing scenarios.

C:\Windows\system32>dism /online /cleanup-image /restorehealth

Deployment Image Servicing and Management tool
Version: 10.0.10586.0

Image Version: 10.0.10586.0

[==========================100.0%==========================]

Error: 0x800f081f

The source files could not be found.
Use the "Source" option to specify the location of the files that are required to restore the feature. For more information on specifying a source location, see Configure a Windows Repair Source.

The DISM log file can be found at C:\Windows\Logs\DISM\dism.log

 

I have since done an in place reinstall and ran sfc and that seems to have fixed the issue.

 

Please mark thread as solved.

 

Thanks for the help guys.