Windows files always corrupted even after repairs?

I notice that after i run these commands in powershell or cmd: sfc /scannow, DISM /Online /Cleanup-Image /RestoreHealth, Get-AppXPackage -AllUsers | Foreach {Add-AppxPackage -DisableDevelopmentMode -Register "$($_.InstallLocation)\AppXManifest.xml"} .

and run sfc /scannow again, I always get this. Attachment 64734 . It seems like my windows is always corrupted and I think that is causing my to get start menu, search menu, and task bar issues after standying by.

Anybody know what's wrong with my computer?

EDIT: I have to do a clean install apparently, also the Get-AppxPackage -AllUsers| Foreach {Add-AppxPackage -DisableDevelopmentMode -Register “$($_.InstallLocation)\AppXManifest.xml”} command broke my apps.

Hi, running the Powershell command has not been recommended since build 10586 (November) came out.. it tends to break apps. You then see @ before their names in the start menu.

To fix this, you are recommended to do an in-place upgrade repair install (you can find instructions in the Tutorials section).

This will:
- keep most of your settings
- keep your programs
- turn system restore off
- restore all Windows apps
- take up to 2 hours
- lose all Windows updates since the last major build (10586)
- create Windows.old

You need a Windows installation medium.

Noted you have a Radeon card: problems have been reported with one dll related to Nvidia cards as regards the cbs .log. You would have to inspect your log to determine what it says.. but that's irrelevant if you do the repair install.

Post back if you still have your other problem.

If you are running an upgrade install a second upgrade might be a "Quick Fix" but eventually not the winning solution a full clean install would be since you mentioned issues with the Start menu. That is a common item with buggy upgrades to 10 it seems!

But before rushing to either of the "Last Resort" options you may want to schedule a run of the Disk Check tool since the SFC found things that tool isn't able to fix while the other tool could since those could be disk errors being reported along side the CBS logs. For the full repair options you would right click on the Start button to bring up the right click menu from that and scroll down to the Command prompt(admin) option. That will prevent any UAC interference when going to schedule the tool for the next startup.

At the dos like command prompt once you have the window open simply type: "chkdsk /r/f" and hit the enter/return key. The two switches R for Repair and F for Fix will see a little bit more repairing tended to and you might possibly be prompted for the Windows media. The fast check to see if the tool needs to be scheduled can be seen to by right clicking on the C drive's icon or thumbnail in any Explorer window and opening up the Tools tab on the properties screen. Simply clicking on the Error checking button will bring up a prompt that will indicate whether or not errors were detected with the option to run a quick on the spot scan.

Night Hawk said:

If you are running an upgrade install a second upgrade might be a "Quick Fix" but eventually not the winning solution a full clean install would be since you mentioned issues with the Start menu. That is a common item with buggy upgrades to 10 it seems!

But before rushing to either of the "Last Resort" options you may want to schedule a run of the Disk Check tool since the SFC found things that tool isn't able to fix while the other tool could since those could be disk errors being reported along side the CBS logs. For the full repair options you would right click on the Start button to bring up the right click menu from that and scroll down to the Command prompt(admin) option. That will prevent any UAC interference when going to schedule the tool for the next startup.

At the dos like command prompt once you have the window open simply type: "chkdsk /r/f" and hit the enter/return key. The two switches R for Repair and F for Fix will see a little bit more repairing tended to and you might possibly be prompted for the Windows media. The fast check to see if the tool needs to be scheduled can be seen to by right clicking on the C drive's icon or thumbnail in any Explorer window and opening up the Tools tab on the properties screen. Simply clicking on the Error checking button will bring up a prompt that will indicate whether or not errors were detected with the option to run a quick on the spot scan.

I ran chkdsk /r /f in cmd but i wasn't able to read the results after it was done. So i ran chkdsk the normal way and no errors found. My windows 10 was a clean install. I'm thinking maybe the usb drive i used or the windows iso i used was originally corrupted

EDIT: ran chkdsk again on windows 10 partition, this time when I'm booted from a different OS and drive. Found errors,

dalchina said:

Hi, running the Powershell command has not been recommended since build 10586 (November) came out.. it tends to break apps. You then see @ before their names in the start menu.

dalchina said:

To fix this, you are recommended to do an in-place upgrade repair install (you can find instructions in the Tutorials section).

This will:
- keep most of your settings
- keep your programs
- turn system restore off
- restore all Windows apps
- take up to 2 hours
- lose all Windows updates since the last major build (10586)
- create Windows.old

You need a Windows installation medium.

Noted you have a Radeon card: problems have been reported with one dll related to Nvidia cards as regards the cbs .log. You would have to inspect your log to determine what it says.. but that's irrelevant if you do the repair install.

Post back if you still have your other problem.

Yea, i notice i start seeing @ for some of my apps. I'm not sure what to look for in the cbs.log

How was the 10 media made up? Did you use the create media option seen with the Media Creation tool or simply wait until after the "Windows.iso" was downloaded and saved to a folder where another app was used?

The quality of the flash drive used often by which brand is selected as I have been finding over the years can have a large impact as well as simply having seen a bad write to any drive. Here I made up the Recovery Drive (s) as well as the 10 media using the same brand of flash drive but using different models by that brand one being a USB 3.0 Threshold 2 Update "4 in 1" that replaced the previous 10240 July 29th "4 in 1"(both editions in both 32/64bit flavors). Some of us worked on that project using the 32bit and 64bit dual edition downloads while the November update has everything rolled into one download.

Initially the 10240 saw both the MC tool and the UltraISO program used originally for the Windows 7 RC and retail USB Installation Keys having bought the key for that program which still works well on 10 after all this time! Here the finding that certain brands of flash drives are utterly useless for seeing usb keys or simply use on any non ac powered usb hubs has ruled out ever buying those again! HP, Memorex, PNY, and some others fit the bill there while San Disk commonly found at Walmarts no less as well as different Kingston Data Traveler and Kingston Hyper X usually work quite well for projects like this as well as for live Linux writes. Even custom installs of some Linux distro direct to one of those two brands will usually go problem free.

As you can see that means being a bit more "picky" or selective on which brands will play a role. But even when you have a 100% good day with the flash drive if something doesn't go on as it should or something trashes a fresh install of Windows you are bound for a rough ride! As seen here initially with upgrade installs of 10 planning for the immediate clean install to follow was a recipe for results while you can still an occasion bad clean install.

The fact that the Disk Check tool even when running that from a previous version finding errors on the 10 drive falls into place as far as the SFC finding the same only not being able to fix those types of errors and of course why MS has different tools. You may still be able to avoid a full clean install if not a repair if you should find something else either a recently added program or update was what saw a bad install which is now being a problem.

Well you could be looking at the need to get a new flash drive. Never worked with a Duracell flash drive but generally Duracell makes batteries not memory like Kingston, Corsair, San Disk making SD type memory cards, etc. that tend to see the best results when having put those up against the lower end stuff made cheaply!

As for the Enterprise edition that wouldn't be seen with the MC tool while you didn't specify which edition you are trying to work with either. When looking at the selection to make between Windows 10, Windows 10 N, Windows 10 Single language edition the Single language is the Home edition only there. The other two are the two Home and Pro editions in both 32bit and 64bit flavors all rolled up into one download where the installer will automatically detect the 32bit or 64bit Home or Pro edition that would go on. IF you have the 32bit Home or Pro the installer would update that to the TH2 Home or Pro 32bit being the 10586 version 1511 build if you only seen the initial 10240 from the July 29th launch last summer.

If you have the 64bit Home or Pro edition the TH2 equivalent will be what goes on as the existing OS is detected to insure the correct upgrade by update path is seen to. For a previous version upgraded to the 10 TH2 the same applies as far as the upgrade path. That's how a 4 in 1 installer works which is what the MC tool download as far as the "Windows.iso" once you select the 10 or 10 N provided you already have the 7, 8, 8.1, or 10 if not 7N, 8N, 8.1N, or 10N on. The Tech Bench options for the 32bit and 64bit downloads there are the dual edition ISOs in either the 32bit or 64bit flavor being 2 in1 instead.

With the Enterprise edition I had the evaluation build for that only here while you are using a company's volume licensing for that edition there. That put things in a totally different category as far as licensing goes as long as it is approved by the company for working at home.

When going to see the next attempt at a clean install make sure any other hard drive present is unplugged! That applies to any drive lacking an OS when not trying to set up a dual boot as well as not wanting the temp installation folders and boot files, mbr or GPT information being scattered across multiple drives! With the SSD being the only hard drive plugged it should rather easy to see the Enterprise edition go on unless the media came out bad. dvd or flash drive? won't matter as far as a bad burn or bad write of the 10 iso.

On another thread I'm helping someone debug the missing Start menu where hardly anything is seen who saw more then one clean install end up seeing the exact same problem repeat itself suggesting the reuse of the exact same media is where the problem is. This is why I had to mention taking a look at that as a potential as well.

imeem said:

I tried doing a in-place upgrade like what @dalchina, But i don't have enough free space on my HDD. So i gess i have to do a clean install when i have the time .

But because i ran Get-AppxPackage -AllUsers| Foreach {Add-AppxPackage -DisableDevelopmentMode -Register “$($_.InstallLocation)\AppXManifest.xml”} before, some of my windows app such as Photo and Calculator, doesn't work anymore. What should i do?

If you have partitions on your drive, you might be able to find some space by reallocating it (perhaps you'll need a 3rd party partition manager. Also, if you already have Windows.old on your c: you might gain a bit by removing that (search for how to do that - you can't just delete it).

Consider what's taking up space - use Windirstat (free) to help you find large files.

Run ccleaner (free) to delete dross.

Perhaps you have a large application - a game e.g. - you can remove.

Maybe you can copy off large personal files- videos, photos.... to an external drive - and delete them.