Announcing Windows 10 Insider Preview Build 15063 for PC and Mobile Insider

I copied install.wim to root of C; and it still can't find it.

jyusa said:

@slicendice: Yours?

INTERSTING! Need to further study this.


SUCCESS

Code:

>DISM /Online /Cleanup-Image /StartComponentCleanup /ResetBase

Deployment Image Servicing and Management tool
Version: 10.0.15063.0

Image Version: 10.0.15063.0

[==========================100.0%==========================]
The operation completed successfully.

FAIL

Code:

>DISM /Online /Cleanup-Image /RestoreHealth

Deployment Image Servicing and Management tool
Version: 10.0.15063.0

Image Version: 10.0.15063.0

[===========================99.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 http://go.microsoft.com/fwlink/?LinkId=243077.

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

FAIL

Code:

>DISM /Online /Cleanup-Image /RestoreHealth /Source:E:\sources\install.wim /LimitAccess

Deployment Image Servicing and Management tool
Version: 10.0.15063.0

Image Version: 10.0.15063.0

[===========================89.8%====================      ]
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 http://go.microsoft.com/fwlink/?LinkId=243077.

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

CLEAN

Code:

>Sfc /scannow

Beginning system scan.  This process will take some time.

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

Windows Resource Protection did not find any integrity violations.

Are they breaking DISM on us, or have commandline options changed, or have they broken paths?

johngalt said:

Are they breaking DISM on us, or have commandline options changed, or have they broken paths?

I don't think the problem is DISM, but the files containing the package and file information, some info still in the list of files needed for full health, but they are not present in install WIM, nor the system.

slicendice said:

I don't think the problem is DISM, but the files containing the package and file information, some info still in the list of files needed for full health, but they are not present in install WIM, nor the system.

No, the problem may not be in DISM itself, but their current modus operandi with the upgrade methodology is still breaking DISM. Which is a tactic Microsoft is quite fond of purporting to use testers on any given IP build lol.

jyusa said:

Apparently, we are not alone. Must need a fix or new commandline option to make it work.

I suspect it has to do with paths, as something it is looking for is no longer where it is looking for it at.

I just tried Store and it barely works. Gave me a message that I need internet which I obviously have but after couple of times it opened. Same thing happened on the phone so I guess they do have some problems although after few tries it updated Kodi and Store itself.