Windows 10: Sysprep issue (miracastview)

I know there has been a lot on this issue, But the workaround doesn't work. Copy the C:\Windows\MiracastView folder from When Syspreping window I get an error says " Package Windows.MiracastView_6.3.0.0_neutral_cw5n1h2txyewy was installed for a
user but not provisioned for all users.
I know there has been a lot of forums on this issue, But the workaround doesn't work. "Copy the C:\Windows\MiracastView folder from a Windows 10 Version 1703 computer to the Windows 10 Version 1709 computer." That didn't work. I have tried removing all the apps Get-AppxPackage -allusers | Remove-AppxPackage (Which I know MS doesn't recommend), but that what fix the issue a few updates ago. Is there another way of fixing this issue without moving files from another computer or removing Miracastview. Also, can you switch over from normal window 10 to window 10 LSTB as an upgrade? I prefer using window LSTB, but ex-coworker made the image in normal window 10. The image has software that we need and no longer can get (Business went under).

I don't understand why this is still an issue. There has been sysprep issue since the beginning of window 10. All of the issue has to deal with window apps. Window 10 is a nightmare for admins.a Windows 10 Version 1703 computer to the Windows 10 Version 1709 computer.

:)

 

Windows 10 Update breaks Sysprep?

I am attempting to image a Dell E7470 with Sysprep to upload to my WDS server.

When I run Sysprep /oobe / shutdown, it completes. However, without Generalize, I won't be able to upload it or deploy it.

When I run Sysprep /oobe /generalize / shutdown, it reports that a fatal error has occurred. The setupact.log lists that the Miracastview app cannot be removed.

I have attempted the Remove-appxpackage commands, but it states that it has been provisioned for the user but not all users. It says to attempt removal with Add / Remove Windows features, but it is not listed there.

I have tried the steps in

https://support.microsoft.com/en-us...w-cause-sysprep-error-windows-10-version-1709

but none of this has worked either.

I guess the answer is to not run any Windows updates before Sysprep and avoid 1709? It appears to be bad news.

Anybody else encounter this? Any other solutions available?

 

Windows 10 1709 sysprep fail

Hi,

I had the same problem, checked the logs and they basically said Windows was unable to remove the Miracast app.

Tried multiple suggestions, nothing worked until I found this:

Failed to sysprep and capture Windows 10 Fall Creators 1709

Basically Microsoft have pushed out their 1709 image without the Miracast app installed, to fix:

• Copy the C:\Windows\MiracastView folder from a working 1703 build into the C:\Windows directory on the 1709 machine
• Restart and then run sysprep

Sysprep should then run successfully!

Josh

 

Welcome to TenForums @Yacob bean

Miracastview would be the 'Wireless Display Media Viewer' - a strange app that appeared in 1703, disappeared again in 1709 and no one seemed to know what it was for...

Cumulative Update KB4016240 Windows 10 v1703 Build 15063.250


@Kari is a sysprep 'guru', but while we for him wait you may like to review this thread...
(if you have not already seen it)
https://social.technet.microsoft.com...in10itprosetup

 

I did check out that Thread. Most of the people got it working by copying the MiracastView to C:\windows. Which didn't work. When doing a PowerShell Command Get-AppxPackage -name "*mir*" Nothing shows up. It's annoying that you have to download 1703 again just to get the MiracastView folder. Why doesn't Microsoft put the MiracastView folder on their website to download?

 

Well, let's hope Kari can suggest a solution then.

 

Windows 10 version 1709 introduced a change regarding built-in admin account that in my opinion is extremely stupid not good and is causing issues: it is now possible to use UWP / Store apps when signed in in Audit Mode for image customization with built-in admin credentials, and it is now possible to switch built-in admin to a Microsoft account. This can't be reversed; there's no way to switch it back to local account or disconnect built-in admin account from MS account.

Not going into issues that users who have accidentally switched built-in admin to a Microsoft account (easily done!) will get when that MS account will be hacked, deleted or is for any reason inaccessible, the change that concerns me more is that because UWP apps, Store and Windows Update now work without issues in Audit Mode / with built-in admin credentials, Windows starts updating UWP apps automatically and as soon as a single UWP app is updated, you will get the app provisioning error if running Sysprep with /generalize switch. Only solution is to remove UWP apps.

You can of course run Sysprep without issues if you do not need to generalize Windows image, but as generalizing is at least to me the single most important reason to run Sysprep in the first place, that's nothing for me.

I have worked around this issue simply by installing Windows 10 in reference machine (I use Hyper-V VM for that) without network connection, creating an additional VHD callet Assets and copying all installers for software I want to / need to add to deployment image plus all theme files, desktop backgrounds and so on to this Assets disk, then adding it to reference VM and doing everything without connecting reference machine to Internet.

Doing it this way will let you sysprep and generalize without app provisioning issues.

On another note, why would you need Miracast app from older version of Windows 10? Casting to Miracast devices is built-in in Windows, you do not need any additional apps or packages for that.

 

I suspect it got included in 1703 in error, see this thread and in particular post #14.

Uninstall Wireless Display Media Viewer