I've added this topic because i've noticed that windows Media player 11

have messed up the sysprep. For two days, i've been searching for what

reason my sysprep wasn't working. At the first startup right after my

sysprep, windows startup gets interrupted by a popup concerning

MSOOBE.exe.



Then, when i reinstalled windows from scratch without WMP11, the

sysprep works fine. If you have a idea why we have a problem, you could

respond to me please.

Thank you!  Thank you!

I too discovered this little "gotcha" a few days back when the master image

that I had been successfully depolying went belly-up.  I had recently updatad

it with all the recent Microsoft Updates, including Media Player 11.  I kept

getting the same error reported above re: msoobe.exe.  After reading your

post, I uninstalled both Media Player 11 components (it actually perfromed a

rollback to v. 10) ran sysprep, and voila!  It works again!  But there seems

to be one caveat.  It did not read my .inf file which was setup to perform in

unnatended mode.  It went through a mini setup.  Perhaps there are some other

recent updates that're still causing me grief.  I'll start the process of

tracking those down.



"lucbourque@hotmail.com" wrote:



> I've added this topic because i've noticed that windows Media player 11

> have messed up the sysprep. For two days, i've been searching for what

> reason my sysprep wasn't working. At the first startup right after my

> sysprep, windows startup gets interrupted by a popup concerning

> MSOOBE.exe.

>

> Then, when i reinstalled windows from scratch without WMP11, the

> sysprep works fine. If you have a idea why we have a problem, you could

> respond to me please.

>

>

I too just encountered this error.  I was syspreping several different

laptops after running recent windows updates (including media player

11) and sure enough, the same sysprep error occured on each laptop.  I

removed media player 11 and re-syspreped....and it works fine when

rolled back to media player 10.  Hope Microsoft is aware of this issue.





Honus on the Sound wrote:[vbcol=seagreen]

> Thank you!  Thank you!

> I too discovered this little "gotcha" a few days back when the master image

> that I had been successfully depolying went belly-up.  I had recently updatad

> it with all the recent Microsoft Updates, including Media Player 11.  I kept

> getting the same error reported above re: msoobe.exe.  After reading your

> post, I uninstalled both Media Player 11 components (it actually perfromed a

> rollback to v. 10) ran sysprep, and voila!  It works again!  But there seems

> to be one caveat.  It did not read my .inf file which was setup to perform in

> unnatended mode.  It went through a mini setup.  Perhaps there are some other

> recent updates that're still causing me grief.  I'll start the process of

> tracking those down.

>

> "lucbourque@hotmail.com" wrote:

>