Is RequestExecutionLevel XP SP2 safe?

reprobate · 26th February 2007, 19:50

Due to a bug namespace handling in the little XML parser that resides in Windows XP SP2 (in CRSS.EXE, specifically, see KB921337), some commonly-formatted manifests can cause SP2 to Blue Screen.

There's workarounds (documented in the KB), but will including RequestExecutionLevel in the script embed XML in the manifest that might run afoul of this MS bug?

Thanks!

Anders · 27th February 2007, 00:38

That is a Visual Studio 2005 bug

reprobate · 27th February 2007, 17:04

It's a CSRSS bug. But if the installers' manifests don't invoke it by redeclaring namespaces like 3 times over, as those generated by VS2005 do (for no particularly good reason), then that's good enough for me.

Thanks!

kichik · 27th February 2007, 18:53

The manifest is safe. It doesn't use the version which CSRSS hates.

Takhir · 28th February 2007, 05:52

This is mt.exe 5.2 bug. MS wrote ( http://support.microsoft.com/kb/921337 ): "When parsing the embedded manifest, its internal memory can be corrupted if it finds a single tag that has two schema properties." but I had the same problem with single schema property. After I installed service, my XP started rebooting even before "Welcome" screen

. So it is highly recomended to replace VS VC/bin mt.exe 5.2 with 6.0 version presenting in SDK/v2.0/bin folder.

26th February 2007, 19:50	#1
reprobate Junior Member Join Date: Jan 2007 Posts: 5	Is RequestExecutionLevel XP SP2 safe? Due to a bug namespace handling in the little XML parser that resides in Windows XP SP2 (in CRSS.EXE, specifically, see KB921337), some commonly-formatted manifests can cause SP2 to Blue Screen. There's workarounds (documented in the KB), but will including RequestExecutionLevel in the script embed XML in the manifest that might run afoul of this MS bug? Thanks!

27th February 2007, 00:38	#2
Anders Moderator Join Date: Jun 2002 Location: ${NSISDIR} Posts: 5,449	That is a Visual Studio 2005 bug IntOp $PostCount $PostCount + 1

27th February 2007, 18:53	#4
kichik M.I.A. [NSIS Dev, Mod] Join Date: Oct 2001 Location: Israel Posts: 11,343	The manifest is safe. It doesn't use the version which CSRSS hates. NSIS FAQ \| NSIS Home Page \| Donate $ "I hear and I forget. I see and I remember. I do and I understand." -- Confucius

Thread Tools	Search this Thread
Show Printable Version Email this Page	Search this Thread: Advanced Search
Display Modes
Linear Mode Switch to Hybrid Mode Switch to Threaded Mode

27th February 2007, 17:04	#3
reprobate Junior Member Join Date: Jan 2007 Posts: 5	It's a CSRSS bug. But if the installers' manifests don't invoke it by redeclaring namespaces like 3 times over, as those generated by VS2005 do (for no particularly good reason), then that's good enough for me. Thanks!

28th February 2007, 05:52	#5
Takhir Major Dude Join Date: Feb 2004 Location: Moscow, Russia Posts: 1,222	This is mt.exe 5.2 bug. MS wrote ( http://support.microsoft.com/kb/921337 ): "When parsing the embedded manifest, its internal memory can be corrupted if it finds a single tag that has two schema properties." but I had the same problem with single schema property. After I installed service, my XP started rebooting even before "Welcome" screen . So it is highly recomended to replace VS VC/bin mt.exe 5.2 with 6.0 version presenting in SDK/v2.0/bin folder.