New
#11
It should not matter which version you have they both contain the same files but as you already have the .esd you can go with that one.
It should not matter which version you have they both contain the same files but as you already have the .esd you can go with that one.
Let me clarify one more time. There are 2 different versions of Windows ISO that you can download.
One from Techbend website and the other is from Media Creation Tool website.
From Techbend, the ISO contains: install.wim
From Media Creation tool, the ISO contains: install.esd
install.wim & install.esd use 2 different methods of compression to package all neccessary files to install/repair Windows. install.esd is smaller in size and faster to download but once they are extracted, they both will have exactly the same files/folders structure.
In the old version od DISM command, it only works with install.wim. The latest version of DISM will work with either one. Since you've already have the ISO downloaded, it does not matter if it's from Techbend or from MCT. People are unaware of the new version of DISM and keep advising to download from Techbend.
As stated from previous post. Check the "Sources" folder, if you have an install.esd then use the 2nd command, if you have install.wim then use the 1st command. The result will be the same, you just have to tell the command what file type to work on.
Just to clarify DISM v10.0.10586 does support .ESD files...In the old version od DISM command, it only works with install.wim. The latest version of DISM will work with either one.
Okay! Partial Success/Improvement!
The ISO image downloaded from Tech Bench with the elevated command "DISM /Online /Cleanup-Image /RestoreHealth /Source:WIM:F:\sources\Install.wim:1 /LimitAccess" said the repairs were completed successfully.
The method using the Windows Download Tool ISO image with the "install.esd" file in the Sources folder did not accomplish the repairs (using the command "DISM /Online /Cleanup-Image /RestoreHealth /Source:ESD:F:\sources\Install.esd:1 /LimitAccess" and said it could not find the files it needed (I forget the exact error message)
I then ran sfc /scannow from the elevated prompt and it reported success as well. I then restarted the machine and again ran "sfc /scannow" as before from the elevated command window and it found NO ERRORS.
I am ecstatic!!! Even this far is FAR more than anyone at Windows chat was able to do (they seemed mosty to want my name and phone number...and to do a factory reset...all of which had nothing to do with the issue or were unacceptable solutions for me).
However, clicking on the "Store" app results only in a quick flash on the screen. Also, most of the other apps, i.e. Edge, Skype, Calculator, etc. report that they cannot be opened with the "built-in Administrator account" and to log out and use a different account. I've no idea what that means at all.
So clearly there is substantial improvement (at least in how Windows "sees" its own image health), yet there are still problems even when "sfc /scannow" finds no integrity violations. I hope it's not asking too much to go a bit further with me in fixing the remaining issues? I've pasted the DISM log again (the CBS log is too large to post now...I don't know why...even when I deleted ALL in the old log beforehand) in case it's different and may help anyone okay?
Attachment 63913
Thanks so very very much!
BB
You can delete CBS.log. Windows will re-create a new one with smaller size then you can post with more up to date info.
From your description it sounds as if you are logged in with the (normally hidden) built in elevated Administrator account rather than a local user with administrator privileges. You need to make sure you add a new user account so that you can log in correctly and try the store and apps again. Here is a tutorial showing you how to do this:However, clicking on the "Store" app results only in a quick flash on the screen. Also, most of the other apps, i.e. Edge, Skype, Calculator, etc. report that they cannot be opened with the "built-in Administrator account" and to log out and use a different account. I've no idea what that means at all.
https://www.tenforums.com/tutorials/5440-user-account-add-windows-10-a.html?filter[1]=User Accounts
Once you have done this you can disable the built in Administrator account using the following tutorial for guidance:
https://www.tenforums.com/tutorials/2969-administrator-account-enable-disable-windows-10-a.html?filter[1]=User Accounts
Hope this helps!
@topgudcp: I didn't actually "delete" the CBS.log (that was not allowed), but I did locate and open the file and delete all the contents before saving the now "empty" text file. I reopened it afterward and it showed nothing inside at all. Then I re-ran the sfc /scannow command from the elevated prompt, and the CBS.log turned out to be about 2.75 MB (when attachments, at least for me, are limited to 2.0 Mb). So that is why I had to settle for posting only the DISM.log, as for some reason it was short enough to be allowed for posting, even though I had not deleted the contents.
@philc43: I have attached a screenshot of my account type, so it appears that I only have a "local" account WITH administrative privileges. Is this somehow preventing me from using any "store/apps" because I am not signed into Microsoft directly (which I REALLY would prefer not to be)? Is this preventing me from using even simple things like a calculator or Skype or Edge, or looking at my own images on my own machine without phoning home all my activities to MS? I am not entirely certain, but before upgrading from 8.1, I'm really pretty sure I could use any software installed on the machine without having a particular account that's essentially "online" all the time. Or am I misunderstanding? All the so-called "apps", including the store, won't open and give the error message that they won't open with the "built-in administrative account" (currently the ONLY account on the machine )and must log out and use a different account type.
Hello and a huge thanks to everyone who contributed to my situation of a corrupted Win X Pro image in this thread from when I tried to upgrade from 8.1 Pro.
For the most part, it appears that the "original" problem of reported errors when running "sfc /scannow" or the DISM "restorehealth" commands from an elevated command prompt seem to be corrected.
It appears I still have issues with any "store/app" not running, but I will start a new thread if I can't find/understand a solution already here when I search for it. Obviously, it seems very strange to me that the image can report itself as healthy, yet most any kind of more "modern" so-called "app" (instead of traditionally installed software) will not open at all (not the store itself, or any of the apps of that type).
Again, thank you so very kindly for your generous assistance...it is so very appreciated!
Did you create a new user account and try opening the apps in the new account?