New
#31
Hi i have the same problem and i am already using windows 10. I am going to try this myself. So let me get this right, once i do all of this i will still have excactly what is on my pc at this moment in time after i have done all of these steps?
If so do i install via the new flash iso......or just directly from windows...or both in that order?
Thanks in advance
Follow this tutorial....
Repair Install Windows 10 with an In-place Upgrade - Windows 10 Forums
Good day. I have a very similar problem and i cant download the link to the image health version 16.02.10
I had the same problem as described on this thread. Here is how I solved it:
- Download the Windows 10 image from Microsoft Tech Bench (those images have the install.wim).
- Run PowerShell with administrative privileges by going to TaskManager -> File -> Run New Task and typing powershell (don't forget to check the option of administrative priveligies). Select Run.
- Now, Run this command:
Code:Dism /Online /Cleanup-Image /RestoreHealth /Source:WIM:X:\sources\install.wim:1 /LimitAccess
Now it should run smoothly.
If you want to know how I got to the solution here it goes:
First, I was getting the following error from DISM (when using /Source:X:\sources\install.wim):
Then I discovered that when I was defining the source as /Source:WIM:X:\sources\install.wim (without the :1) it wouldn't recognize the source and would even say that it didn't exist:Code: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
Finally I found the DISM GUI tool, and opened the wim file to discover that it packed 2 versions of Windows 10: Pro (Index 1) and Home (Index 2)Code:Error: 87 An error occurred while processing WIM:C:\RestoreImage\install.wim. The specified path was not found. Ensure that the argument is valid and that the path exists. The DISM log file can be found at C:\Windows\Logs\DISM\dism.log
So I realized that it would need an explicit specificatio of the index, hence the solution.
Hope it helps!
I have just noticed this issue after performing sfc/scannow. Should note that I did a reset of Win10 to no avail, appears only the iso upgrade works.
Two questions, please:
- What causes this issue ? Updates ?
- Will the major update scheduled approx. 29 July automatically correct this issue ?
Thanks for the reply.
Performance is not really effected. I have a Win10 iso already made for the inplace upgrade. Just seems like a hassle to correct the issue.
Anyone know what causes the issue ? MSN upgrades ?