Re: Missing Security Tab for drive/folders

Russell,

We are going to be trying forever to guess what components may be missing from your image. You basically listed all the tricks to
make Security tab working.
Hope you've got NTFS on target media. Winlogon/Explorer shell are also in my assumptions.

I'd suggest you to perform a comparison to XP Pro with regards to the feature you are missing.
Perform the following steps on XP Pro machine and on your XPe device:
- Open Explorer (or do that from Desktop)
- Run Regmon
- Right click on a folder
- Capture the Regmon log

Then compare the logs you captured on XP Pro and XPe machines (there will certainly be much of garbage :-( ) and analyze the
differences.
You can post the diff here and we can help you to figure out what's missing.

--
Regards,
KM, BSquare Corp.


> I still haven't figured this out, so if any of you have an answer, please
> help me.
>
> "RussR" <nospam@xxxxxxxxxx> wrote in message
> news:OXz8a2YMFHA.576@xxxxxxxxxxxxxxxxxxxxxxx
> > Hi Folks,
> >
> > For the life of me, I cannot figure out why the Security tab is missing in
> > the properties for a drive or folder.
> >
> > Let me share first what components I have included. I am using XPe SP1
> >
> > I've included the following components and registry data:
> > Security Shell Extension
> > Primitive MPRUI
> > Drive\shellex\ContextMenuHandlers\Sharing registry data wtih REG_SZ
> > set to {f81e9010-6ea4-11ce-a7ff-00aa003ca9f6}
> > Drive\shellex\PropertySheetHandlers\Sharing registry data with REG_SZ
> > set to {f81e9010-6ea4-11ce-a7ff-00aa003ca9f6}
> > Windows Security Config Editor Client Engine
> > Windows Security Config Editor Engine
> > Security Accounts manager Client
> > Security Accounts Manager Server Library
> > Msxml libraries and components
> >
> > I even tried manually register of rshx32.dll. What on earth am I doing
> > wrong as I just cannot get that security tab to show up. I've searched
> > through the newgroup, and already tried all the recommended solutions that
> > worked for others.
> >
> > Thanks,
> > Russell
> >
> >
>
>


.