Update rollup issue

[Guest]

After upgrading with Update Rollup 1 on top of FP 2007 I have a strange issue
with and image that has run fine under vmware. I upgraded the slx to use all
the updated components and built an image. The shell is a custom .net 2.0
app. fba seems to process just fine and the custom shell eventually runs. I
have a button on the custom shell app that runs a cmd prompt so that I may
finish some customization before etpreping the image (it's an eltorito
image). Before the upgrade the cmd prompt opened just fine, after the
upgrade, I get an access denied Win32Exception
fromSystem.Diagnostics.Process.StartWithShellExecuteEx. Is there some issue
with EWF? I'm at a loss.

Thanks

Peter

 

[Guest]

More info:

I had saved the slx file of my image prior to the upgrade and re-verified
that it still works, i.e. doesn't throw the access denied error when I try
and start a cmd prompt from my custom c# shell. The following components were
upgraded in the project:

FBA from R3333 to R4010
HTML rendering engine - kb928090 from R3351 to R4010
Microsoft Line Services from R620 to R4010
Primitive: Advpack from R2890 to R4010
Primitive: Browseui from R3351 to R4010
Primitive: DXTRANS.DLL from R3351 to R4010
Primitive: iedkcs32.dll from R3333 to R4010
Primitive: IEXPLORER.EXE from R3333 to R4010
Primitive: IMGUTIL.DLL from R3333 to R4010
Primitive: INETCPL.CPL from R3333 to R4010
Primitive: INSENG.DLL from R3351 to R4010
Primitive: jscript.dll R3333 to R4010
Primitive: JSPROXY.DLL from R3351 to R4010
Primitive: MSHTA.EXE from R3333 to R4010
Primitive: MSRATING.LL from R3351 to R4010
Primitive: Shdocvw from R3351 to R4010
Primitive: Shlwapi from R3351 to R4010
Primitive: vbscript.dll from R3333 to R4010
Urlmon library from R3351 to R4010
Windows subsystem from R3333 to R4010
Wininet library from R3351 to R4010

Resolved all dependencies.

Thanks

Peter

 

[KM]

Peter,

A quick question - are you able to launch CMD on the newest image at all? For instance, try to launch it as the shell instead of
your application (basically just change the [HKLM\Software\Windows NT\CurrentVersion\Winlogon],"Shell" key).

If it is launched just fine, the problem is about either your app or the .Net libraries you use.
If not, you are either missing something (unlikely) or something else going on there. That is where I'd suggest you to take a look
at FBALog.txt and setupapi.log files to see if there were ay issues with any component installation.

After all, you always have a step-by-step laborious approach where you can only upgrade component-by-component in your image config
keeping deploying the image on the device for testing purposes after each step. This way you'd know what the component upgrade made
the difference.