none
Unable to Sysprep after Fall Creator Update Due To Miracast RRS feed

  • Question

  • Hi,

    I have upgraded a Windows 10 PC with Fall Creator Update. The image I upgraded was fresh without and additional programs except Office 2016 and a handful of fonts.

    I want to create a base image from it.

    The Sysprep OOBE + Generalise fails as it cannot validate Windows. The setupact log pins the blame on Micracast:

    2017-10-23 10:51:05, Info                  SYSPRP Entering SysprepGeneralizeValidate (Appx) - validating whether all apps are also provisioned.

    2017-10-23 10:51:05, Error                 SYSPRP Package Windows.MiracastView_6.3.0.0_neutral_neutral_cw5n1h2txyewy was installed for a user, but not provisioned for all users. This package will not function properly in the sysprep image.

    2017-10-23 10:51:05, Error                 SYSPRP Failed to remove apps for the current user: 0x80073cf2.

    2017-10-23 10:51:05, Error                 SYSPRP Exit code of RemoveAllApps thread was 0x3cf2.

    2017-10-23 10:51:05, Error                 SYSPRP ActionPlatform::LaunchModule: Failure occurred while executing 'SysprepGeneralizeValidate' from C:\Windows\System32\AppxSysprep.dll; dwRet = 0x3cf2
    2017-10-23 10:51:05, Error                 SYSPRP SysprepSession::Validate: Error in validating actions from C:\Windows\System32\Sysprep\ActionFiles\Generalize.xml; dwRet = 0x3cf2
    2017-10-23 10:51:05, Error                 SYSPRP RunPlatformActions:Failed while validating Sysprep session actions; dwRet = 0x3cf2
    2017-10-23 10:51:05, Error      [0x0f0070] SYSPRP RunExternalDlls:An error occurred while running registry sysprep DLLs, halting sysprep execution. dwRet = 0x3cf2

    2017-10-23 10:51:05, Error      [0x0f00d8] SYSPRP WinMain:Hit failure while pre-validate sysprep generalize internal providers; hr = 0x80073cf2
    2017-10-23 10:51:15, Info       [0x0f0052] SYSPRP Shutting down SysPrep log
    2017-10-23 10:51:15, Info       [0x0f004d] SYSPRP The time is now 2017-10-23 10:51:15

    Getting more information in PowerShell I get the following for

     

    PackageFullName        : Windows.MiracastView_6.3.0.0_neutral_neutral_cw5n1h2txyewy
    PackageUserInformation : {S-1-5-21-2325304736-1218276920-2303212629-500 [Administrator]: Installed(pending removal)}

    I try to remove-appx Miracast and it has an error. Looking at the logs I get:

    Time                      ID           Message
    ----                      --           -------
    23/10/2017 10:12:34 AM    603          Started deployment Remove operation on a package with main parameter: Windows.MiracastView_6.3.0.0_neutral_neutral_cw5n1h2txyewy and Options: 0 and 0.
                                           See http://go.microsoft.com/fwlink/?LinkId=235160 for help diagnosing app deployment issues.
    23/10/2017 10:12:34 AM    10002        Creating Resiliency File
                                           C:\ProgramData\Microsoft\Windows\AppRepository\3546fe49-8d75-42f3-87eb-3ddddd3bf72b_S-1-5-21-2325304736-1218276920-2303212629-500_1.rslc for Remove
                                           Operation on Package Windows.MiracastView_6.3.0.0_neutral_neutral_cw5n1h2txyewy.
    23/10/2017 10:12:34 AM    607          Deployment Remove operation on package Windows.MiracastView_6.3.0.0_neutral_neutral_cw5n1h2txyewy has been de-queued and is running for user SID
                                           S-1-5-21-2325304736-1218276920-2303212629-500.
    23/10/2017 10:12:34 AM    475          error 0x80070002: Reading manifest from location:
                                           C:\ProgramData\Microsoft\Windows\AppRepository\Windows.MiracastView_6.3.0.0_neutral_neutral_cw5n1h2txyewy.xml failed with error: The system cannot find
                                           the file specified.
                                           .
    23/10/2017 10:12:34 AM    341          Cannot open manifest file for package Windows.MiracastView_6.3.0.0_neutral_neutral_cw5n1h2txyewy (0x80070490). Using manifest from StateRepository
                                           instead.
    23/10/2017 10:12:34 AM    343          Cannot open manifest file for package Windows.MiracastView_6.3.0.0_neutral_neutral_cw5n1h2txyewy (0x80070490). Using manifest from StateRepository
                                           instead.
    23/10/2017 10:12:34 AM    605          The last successful state reached was BundleProcessed. Failure occurred before reaching the next state Indexed. hr: 0x80070490
    23/10/2017 10:12:34 AM    401          Deployment Remove operation with target volume C: on Package Windows.MiracastView_6.3.0.0_neutral_neutral_cw5n1h2txyewy from:   failed with error
                                           0x80070490. See http://go.microsoft.com/fwlink/?LinkId=235160 for help diagnosing app deployment issues.
    23/10/2017 10:12:34 AM    404          AppX Deployment operation failed for package Windows.MiracastView_6.3.0.0_neutral_neutral_cw5n1h2txyewy with error 0x80073CFA. The specific error text
                                           for this failure is: Deployment Remove operation with target volume C: on Package Windows.MiracastView_6.3.0.0_neutral_neutral_cw5n1h2txyewy from:
                                           failed with error 0x80070490. See http://go.microsoft.com/fwlink/?LinkId=235160 for help diagnosing app deployment issues.

     

    I have found 1 other reference to this issue - a user posted it on a forum 4 days ago with no response. I have replicated this on several computers - all Dell Latitudes.

    Any suggestions?

    Garry

    Monday, October 23, 2017 4:04 AM

Answers

  • I've been wrestling with this issue this afternoon.

    I have at least discovered that copying the C:\Windows\MiracastView folder from another computer into the same place on the image master then rebooting the device allows Windows to finish uninstalling it.

    SysPrep then gets passed the validation error!

    Mine has a different fatal error shortly afterwards, but hopefully the above helps someone else. 

    • Marked as answer by Garry McK Tuesday, October 24, 2017 2:43 AM
    Monday, October 23, 2017 5:54 AM

All replies

  • I've been wrestling with this issue this afternoon.

    I have at least discovered that copying the C:\Windows\MiracastView folder from another computer into the same place on the image master then rebooting the device allows Windows to finish uninstalling it.

    SysPrep then gets passed the validation error!

    Mine has a different fatal error shortly afterwards, but hopefully the above helps someone else. 

    • Marked as answer by Garry McK Tuesday, October 24, 2017 2:43 AM
    Monday, October 23, 2017 5:54 AM
  • I am also having the same problem. Please let me know if you figure it out.
    Monday, October 23, 2017 6:17 PM
  • Thanks. Worked fine with me and SysPrep finished.
    Tuesday, October 24, 2017 2:43 AM
  • I must be missing something.  What folder did you copy?  I'm finding no C:\Windows\Miracast folder, and I can't figure out which folder it'd be under C:\Program Files\WindowsApps.

    I'm having this same issue, and really need to find a solution.  Any help is appreciated!

    EDIT: I figured it out.  While I couldn't find the C:\Windows\Miracast folder on another computer that had been upgraded to 1709, I hadn't yet pulled the Windows.old folder from that computer, and in there, the Windows\Miracast folder DID exist.  I pulled from there, pushed to the Image Master computer, and voila!  Big thanks to blawrencevic for the info that pointed me in the right direction.


    • Edited by JCT3 Tuesday, October 24, 2017 3:00 PM
    Tuesday, October 24, 2017 1:25 PM
  • Thanks, I got past the MiraCast error by copying the folder. Now I get this error:

    Microsoft.SurfaceWirelessDisplayAdapter_3.0.124.0_x64__8wekyb3d8bbwe was installed for a user, but not provisioned for all users.

    I did not see a Surface folder in Windows. Any ideas?
    Wednesday, October 25, 2017 8:12 PM
  • Genius - thank you for this!
    Friday, October 27, 2017 7:40 PM
  • Thanks blawrencevic! Image is now capturing without a fuss.

    @Jacob Miller, did you check if it's in the C:\Program Files\WindowsApps directory?


    Monday, October 30, 2017 4:19 PM
  • Can you please help me. I am getting same error:

    Package Windows.MiracastView_6.3.0.0_neutral_neutral_cw5n1h2txyewy was installed for a user, but not provisioned for all users. This package will not function properly in the sysprep image.

    I have copied MiracastView folder from one machine to the c:\Windows but no luck. 

    Please help me to resolve this issue.

    Tuesday, October 31, 2017 11:12 AM
  • Can you please help me. I am getting same error:

    Package Windows.MiracastView_6.3.0.0_neutral_neutral_cw5n1h2txyewy was installed for a user, but not provisioned for all users. This package will not function properly in the sysprep image.

    I have copied MiracastView folder from one machine to the c:\Windows but no luck. 

    Please help me to resolve this issue.

    Tuesday, October 31, 2017 11:23 AM
  • Thanks very much, this worked!

    I went to a 1703 workstation and copied the C:\Windows\MiracastView to the 1709 PC, (on which the folder did not even exist) and then I was able to sysprep without issue.
    Wednesday, November 1, 2017 3:19 PM
  • Hi,

    Here is what I did to get sysprep working again

    From a 1703 machine, copy and paste the "c:\windows\miracastview" directory into the following two 1709 directory

    "c:\windows" (missing in here) 

    "c:\windows.old\windows" (not missing but replace anyways)

    Reboot and run sysprep


    Wednesday, November 1, 2017 9:57 PM
  • I too wasn't successful after copying the folder from an old machine.

    After a bit of digging, I was able to remove it manually by following the instructions at http://alexappleton.net/post/159702702033/windows-10-pro-remove-wireless-display-media (you will still need to place the folder).

    I was still unable to sysprep, but it was because sysprep couldn't remove Microsoft.3dViewer. After running the steps to remove that app using powershell as system I got past those issues.

    Friday, November 3, 2017 5:24 PM
  • C:\Program Files\WindowsApps is a hidden folder, so please copy/paste to locate. I found  the Microsoft.SurfaceWirelessDisplayAdapter_3.0.124.0_x64__8wekyb3d8bbwe folder there.

    I still cannot sysprep the machine. I wonder the difference between those who copied over C:\Windows\MiracastView and sysprep worked to those who did and sysprep did not work.

    Friday, November 3, 2017 9:55 PM
  • Thanks for your advise Blawrencevic. It got me past the Windows Store own app update breaking v1709 when doing a sysprep on an upgraded image. My first attempt imploded as I was using past experiences on pre v1607 where registry modications are needed, etc. No registry changes should get done on v1709 else it will imploded. Using steps I listed below worked successfully and third repeated without any hitches. Below are my notes how to do successfully using your posting.

    1. When performing an OS Upgrade on a base image, after first sign on as your admin, IMMEDIATELY turn off Windows Store' updating of apps. After all tweaks/programs updated, etc. I run the Windows Cleanup utility to clear the Windows.OLD, it saves ~15 GB off on the C drive as unneeded on PCs to obtain the image..

    2. Admin Powershell to see if Pending Uninstall for Miracast
    -> Get-AppxPackage -AllUsers | Where-Object {$_.Name -eq "Windows.Miracastview"}
    2b. if PENDING UNINSTALL, Fix by copying from a windows.old or another v1703 PC the C:\windows\miracast into this affected Base Image PC that errors on sysprepping.
    -Then reruning step 3 will now be blank confirming it uninstalled. If not, reboot then rerun Get-AppxPackage to confirm Miracastview is blank.
    3. Admin Powershell to see if STAGED for the Get Office app aka Office Hub.
    -> Get-AppxPackage -AllUsers | Where-Object {$_.Name -eq "Microsoft.MicrosoftOfficeHub"}
    3b. If STAGGED. Remove it by -> Get-AppxPackage -AllUsers | Where-Object {$_.Name -eq "Microsoft.MicrosoftOfficeHub"} | remove-appxpackage
    4. Sysprep will error one more time about the XBoxOneSmartGlass. Remove it. If you didnt turn off Store's updating of apps fast enough, there will be tons of apps that will cause sysprep to error.
    -> Remove-AppxPackage Microsoft.XboxOneSmartGlass_2.2.1702.2004_x64__8wekyb3d8bbwe
    5. Now perform the sysprep generalize successfully on shutdown and capture image.

    Sunday, November 5, 2017 5:07 PM
  • I was able to resolve this issue by copying the MiracastView folder from another machine to the image source machine using a USB stick and then rebooting and trying again.
    Monday, November 6, 2017 3:47 PM
  • Thanks for your advise Blawrencevic. It got me past the Windows Store own app update breaking v1709 when doing a sysprep on an upgraded image. My first attempt imploded as I was using past experiences on pre v1607 where registry modications are needed, etc. No registry changes should get done on v1709 else it will imploded. Using steps I listed below worked successfully and third repeated without any hitches. Below are my notes how to do successfully using your posting.

    1. When performing an OS Upgrade on a base image, after first sign on as your admin, IMMEDIATELY turn off Windows Store' updating of apps. After all tweaks/programs updated, etc. I run the Windows Cleanup utility to clear the Windows.OLD, it saves ~15 GB off on the C drive as unneeded on PCs to obtain the image..

    2. Admin Powershell to see if Pending Uninstall for Miracast
    -> Get-AppxPackage -AllUsers | Where-Object {$_.Name -eq "Windows.Miracastview"}
    2b. if PENDING UNINSTALL, Fix by copying from a windows.old or another v1703 PC the C:\windows\miracast into this affected Base Image PC that errors on sysprepping.
    -Then reruning step 3 will now be blank confirming it uninstalled. If not, reboot then rerun Get-AppxPackage to confirm Miracastview is blank.
    3. Admin Powershell to see if STAGED for the Get Office app aka Office Hub.
    -> Get-AppxPackage -AllUsers | Where-Object {$_.Name -eq "Microsoft.MicrosoftOfficeHub"}
    3b. If STAGGED. Remove it by -> Get-AppxPackage -AllUsers | Where-Object {$_.Name -eq "Microsoft.MicrosoftOfficeHub"} | remove-appxpackage
    4. Sysprep will error one more time about the XBoxOneSmartGlass. Remove it. If you didnt turn off Store's updating of apps fast enough, there will be tons of apps that will cause sysprep to error.
    -> Remove-AppxPackage Microsoft.XboxOneSmartGlass_2.2.1702.2004_x64__8wekyb3d8bbwe
    5. Now perform the sysprep generalize successfully on shutdown and capture image.


    Perfect ! worked at last.
    Thursday, November 23, 2017 3:31 PM
  • I downloaded the 1709 ISO and applied it to my Task Sequence, and Sysprep now works.

    Microsoft Premier Support basically told me that you can't sysprep a Windows 10 pc after any major update like the Fall Creators update.  You should install a fresh OS.  WDS made this very easy.  I've been struggling with this since the FCU 1709, I should have called M$ Earlier.


    Wednesday, November 29, 2017 5:59 PM
  • Excellent thanks, that's all I needed to do, copy the folder there from another machine and reboot.  Job's a good'n'!

    Somewhere out there...

    Friday, December 1, 2017 10:54 AM
  • There are 2 valid workarounds
    • Workaround 1 of 2:

      Copy Windows.MiracastView_6.3.0.0_neutral_neutral_cw5n1h2txyewy.xml from C:\Windows.old\ProgramData\Microsoft\Windows\AppRepository\ into  C:\ProgramData\Microsoft\Windows\AppRepository

      OR

    • Workaround 2 of 2

      copy the C:\Windows\MiracastView to the 1709 PC from a 1703 workstation, then reboot the device which allows Windows to finish uninstalling it.
    Problem is being fixed in RS4.
    • Proposed as answer by jconrod Tuesday, December 5, 2017 8:24 PM
    Friday, December 1, 2017 4:51 PM
  • Thanks.  Workaround 1 didn't work for me but workaround 2 did.
    Tuesday, December 5, 2017 8:25 PM
  • Make sure you reboot after the copy.  Also I hit this thread first after dealing with AppX issues.  Those are typically dealt with a clean install, using the built-in Administrator account and deleting the created account.

    PROBLEM: Someone (probably at Microsoft) decided to remove C:\Windows\MiraCastView from 1709 deployment, when it goes from staged to pending removal, it tries to create a "Resiliency File" using a file it can't find.  This was seen in the Get-AppXLog command.

    SOLUTION: Copy the folder C:\Windows.old\MiraCastView to C:\Windows\MiraCastView and reboot your machine.  You should be able to sysprep if you have no other AppX problems.  If you don't have Windows.old (clean install), you'll need to copy from another machine that has been deployed (at least the manifest file).

    Tuesday, December 5, 2017 10:11 PM
  • The first time I tried copying C:\Windows\MiraCastView to the fall update (v1709) from v1703 it worked, but....

    I had to do a repair install of v1709 an now that trick doesn't work. I don't have Windows.old or OS.old as I ran Disk Cleanup but I do still have the 1703 MiraCastView folder. I've tried uninstall/deleting it in the new fall update an reapplying it but to no avail. Any ideas? Other than a fresh install....or is that the only solution til M$ puts out a KB?


    • Edited by tazmo8448 Friday, December 8, 2017 6:25 AM
    Friday, December 8, 2017 6:25 AM
  • I came cross this same issue creating a WDS image of Windows 10.  I had a 1703 image, ran the OOBE and booted to Windows normally.  I then ran the Feature Update from Settings up to 1709 in the normal way.

    I resolved this by copying the C:\Windows.old\Miracast folder in to the C:\Windows folder and then using Sysprep to Reboot into Audit Mode.  Once in Audit mode I opened the classic System tab and Advanced settings, to remove the local admin account I'd been using to run the updates etc.  Once this profile had been removed, leaving the Audit Mode Administrator profile there as you're already signed in to it, I could run Sysprep/Generalize and OOBE as normal.

    Friday, December 8, 2017 10:33 AM
  • great. amazing, this worked for me. 
    Friday, January 5, 2018 11:36 AM
  • thank you for the post.
    
    I ran into this issue while updating my windows templates. My sysprep script failed. Upon examining the sysprep logs, it was this package Windows.MiracastView_6.3.0.0_neutral_neutral had pending uninstall status. 
    
    https://stackoverflow.com/questions/46818294/sysprep-failure-on-windows-miracastview
    
    So  "Fall Creator Update" removed the content of C:\Windows\MiracastView. Therefore, uninstallation for administrator profile could not succeed. I deployed another Windows 10 VM from the pre-update template. Once I copied the folder to my source VM and rebooted, I found that C:\Windows\MiracastView was gone. I relaunched my Sysprep script which finished this time with no issues. 
    
    I've also deployed test VM from a newly created template - no issues with automated setup.
    
    Thank you for advice - saved much time.
    



    Thursday, January 11, 2018 5:31 AM
  • Hello,

    I spent my whole afternoon on that crap, I just can't get rid of this message :

    2018-01-11 18:15:15, Info                  SYSPRP Entering SysprepGeneralizeValidate (Appx) - validating whether all apps are also provisioned.
    2018-01-11 18:15:16, Error                 SYSPRP Package Windows.MiracastView_6.3.0.0_neutral_neutral_cw5n1h2txyewy was installed for a user, but not provisioned for all users. This package will not function properly in the sysprep image.
    2018-01-11 18:15:16, Error                 SYSPRP Failed to remove apps for the current user: 0x80073cf2.
    2018-01-11 18:15:16, Error                 SYSPRP Exit code of RemoveAllApps thread was 0x3cf2.
    2018-01-11 18:15:16, Error                 SYSPRP ActionPlatform::LaunchModule: Failure occurred while executing 'SysprepGeneralizeValidate' from C:\Windows\System32\AppxSysprep.dll; dwRet = 0x3cf2
    2018-01-11 18:15:16, Error                 SYSPRP SysprepSession::Validate: Error in validating actions from C:\Windows\System32\Sysprep\ActionFiles\Generalize.xml; dwRet = 0x3cf2
    2018-01-11 18:15:16, Error                 SYSPRP RunPlatformActions:Failed while validating Sysprep session actions; dwRet = 0x3cf2
    2018-01-11 18:15:16, Error      [0x0f0070] SYSPRP RunExternalDlls:An error occurred while running registry sysprep DLLs, halting sysprep execution. dwRet = 0x3cf2
    2018-01-11 18:15:16, Error      [0x0f00d8] SYSPRP WinMain:Hit failure while pre-validate sysprep generalize internal providers; hr = 0x80073cf2
    2018-01-11 18:15:18, Info       [0x0f0052] SYSPRP Shutting down SysPrep log

    admin Powershell says :

    PS C:\Users\Administrateur> get-appxpackage -AllUsers | where PackageFullName -eq Windows.MiracastView_6.3.0.0_neutral_neutral_cw5n1h2txyewy


    Name                   : Windows.MiracastView
    Publisher              : CN=Microsoft Windows, O=Microsoft Corporation, L=Redmond, S=Washington, C=US
    Architecture           : Neutral
    ResourceId             : neutral
    Version                : 6.3.0.0
    PackageFullName        : Windows.MiracastView_6.3.0.0_neutral_neutral_cw5n1h2txyewy
    InstallLocation        : C:\Windows\MiracastView
    IsFramework            : False
    PackageFamilyName      : Windows.MiracastView_cw5n1h2txyewy
    PublisherId            : cw5n1h2txyewy
    PackageUserInformation : {S-1-5-21-2105204792-4017142548-467776215-1000
                             [S-1-5-21-2105204792-4017142548-467776215-1000]: Installed(pending removal),
                             S-1-5-21-2105204792-4017142548-467776215-1001 [tt999999]: Installed(pending removal)}
    IsResourcePackage      : False
    IsBundle               : False
    IsDevelopmentMode      : False
    IsPartiallyStaged      : False
    SignatureKind          : System
    Status                 : Ok

    I tried to copy C:\Windows\MiracastView from a 1703 pc to C:\Windows and C:\Windows.old\Windows and to reboot various times but nothing seems to work as it's still there !

    Thursday, January 11, 2018 5:25 PM
  • In fact it says tht it's a system app that can't be uninstalled per-user and that an admin could be able to remove it via the functionality panel (but there's nothing about miracast view there). It also say that maybe it's impossible to remove it. I'm stuck. Any further idea ? Otherwise I'll have to get back to 1703. I just can't make a new image from blank (70+ software installed)

    Thanks

    

    Friday, January 12, 2018 12:53 PM

  • .- Hi, Nicolas, I had the same error. Work now for me...

    ERROR Timeline, like u:

    .- Updating and image from 1703 -> 1709.

    .- From audit mode --> sysprep generalize --> failed --> because "Miracast not provisioned" but installed for one user.

    .- After Clean disk manager, windows.old folder gones up, so i was missing C:\Windows\MiracastView, and windows.old

    .-  Powershell command:  get-appxpackage -allusers *mira*

       I saw "Installed(pending removal)" for administrator and 2 test-users more. ( 3 users pending removal )

    .- remove-appxpackage Windows.MiracastView_6.3.0.0_neutral_neutral_cw5n1h2txyewy

       FAILED!!! cant remove miracasteview for thouse 3 users.

    SOLUTION FOR ME:

    .- I COPIED C:\Windows\MiracastView, from other previus master v1703.

    .- Reboot not works, still MiracastApp pendin removal.

    .- I made login whith users, one by one ( administrator, user1, user2 ), but this time, i could make:

    remove-appxpackage Windows.MiracastView_6.3.0.0_neutral_neutral_cw5n1h2txyewy --> works.

    .- So, "get-appxpackage -allusers *mira*" --> returns me an empty result.

    .- NO miracast dependencies. --> sysprep should not fail at least, for that reason.






    • Edited by Angeloxo_es Tuesday, January 16, 2018 5:08 PM
    Tuesday, January 16, 2018 5:03 PM
  • I'm having this same problem with Win10 version 1709. I'm trying to move a hard drive to a new system.

    The problem is that my Windows.old folder is basically empty now and I don't have a machine running 1703 to get the C:\Windows\MiracastView folder from.

    Anything else I can try? Someone at Stack Overflow (https://stackoverflow.com/questions/48306170/windows-10-fall-patch-sysprep-fails-miracastview-issue) said to edit the generalize.xml file in the Sysprep folder but I don't know how to gain permission to edit that file.

    Thursday, January 18, 2018 5:29 PM
  • @Lapdog65 - Microsoft Premier Support is wrong - you should ask for your money/incident back. See this Microsoft sysprep support document. This is a mistake on Mircrosoft's part in the 1709 upgrade process.
    Tuesday, January 23, 2018 4:44 PM
  • Hi Garry

    I've had same error and written a blog about it.

    How to solve sysprep error

    Wednesday, February 14, 2018 10:23 AM
  • THANK YOU so much this saved me tons of time and effort and now My 1709 64-bit image is syspreping
    Tuesday, February 27, 2018 6:10 PM
  • Thanks. this actually work for me. I have the MiracastView problem when running sysprep too. the folder is missing from c:\windows after the 1709 creator update. Putting it back and restart actually worked. 

    thanks. 

    Monday, March 5, 2018 7:00 PM
  • I too experienced the MiracastView error when running SYSREP and tried all sorts or solutions listed in this forum and others. Too many hours, then I saw a post recommending downloading the latest Windows 10 iso. I did and rebuilt my image for the organization that I volunteer my skills for. Now MiracastView is gone, however the Microsoft Store app allows other products to invade your computer and they too will cause similar SYSPREP errors. I disconnected my Ethernet and uninstalled a dozen or more of these unsolicited apps. The final result, SYSPREP completed successfully and I have a new image at the 1709 level. I hope this helps others with their work, since I had almost given up on finding a solution.
    • Edited by Caesargw Saturday, March 24, 2018 10:11 PM
    Saturday, March 24, 2018 10:10 PM
  • I tried to use Sysprep Audit Mode and now my PC will not boot.  Getting message that the Windows could not complete the installation.

    DON'T TRY THIS.

    Wednesday, March 28, 2018 9:30 PM
  • Amazing that windows is always broken in new strange ways!

    Built by complete morons.

    Friday, June 29, 2018 7:55 AM
  • I just had the same problem after an upgrade in Osx Bootcamp (a fresh install of 1709 doesn't mount in Osx).  There's a Microsoft article about the Sysprep Miracast App bug.  Just copy the folder from 1703.  https://support.microsoft.com/en-us/help/4057974/miracastview-cause-sysprep-error-windows-10-version-1709





    • Edited by JS2010 Wednesday, August 8, 2018 7:45 PM
    Wednesday, August 8, 2018 7:44 PM
  • I have this problem also and moving folders didnt work.

    Tuesday, January 29, 2019 9:54 PM