New
#11
Works in command prompt (impossible)?Code:regsvr32 CSEShellNsExt.dll
Works in command prompt with admin rights?
Works in command prompt (impossible)?Code:regsvr32 CSEShellNsExt.dll
Works in command prompt with admin rights?
The elevation process normally changes the directory to C:\Windows\system32 (unless you do something like this). Most likely, neither of the cmd windows shown in your OP went thru the elevation process. I should have noticed that the second screenshot in your OP (the one that has Administrator: in the title) is starting in a non-standard directory.
My guess is that both give you the desktop's contents because you are operating in a non-recommended way:
1) You have User Account Control turned off and...
...you are logged in using an account with admin rights*.
2) You are logged in using the built in Administrator account*.
3) You have User Account Control turned off and...
...you are logged in using an account with standard rights**.
*Thus everything runs at either the system integrity level or the high integrity level. The cmd window was launched via explorer. Explorer was already running at a high integrity level. The cmd prompt window inherited its high integrity level from explorer (desktop). The cmd prompt window did not go thru the elevation process. For an admin user with the UAC off (or for the built in Administrator account), both ways of starting the "dir" bat file would yield the desktop's contents.
**Not really plausible since post #3 states that you are "the only user and a full Admin", but a standard account would not be able to elevate a process if UAC is turned off - not without jumping thru some hoops. Double clicking on a the "dir" bat file would run it in at the medium integrity level. Right clicking and selecting "run as admin..." will transparently fail to elevate. The cmd window was launched via explorer. Explorer was running at a medium integrity level. The cmd prompt window inherited its medium integrity level from explorer (desktop). The cmd prompt window did not go thru the elevation process. For a standard user with the UAC off, both ways of starting the "dir" bat file would yield the desktop's contents.
Of course, I could be wrong about all of the above
So, like I asked before:
But maybe I was not clear. I wanted you to test this code in a bat file.
Code:CD "C:\Program Files\Dassault Systemes\IEFClientV6R2013xv3\bin" regsvr32 /s CSEShellNsExt.dll
C:
CD "C:\Program Files\Dassault Systemes\IEFClientV6R2013xv3\bin"
regsvr32 CSEShellNsExt.dll
does work from bat file (elevated)?
the batfile is already in "C:\Program Files\Dassault Systemes\IEFClientV6R2013xv3\bin" ? that's why you see "C:\Program Files\Dassault Systemes\IEFClientV6R2013xv3\bin" in the output... quite normal.
But maybe I was not clear. I wanted you to test this code in a bat file.
[/QUOTE]Code:CD "C:\Program Files\Dassault Systemes\IEFClientV6R2013xv3\bin" regsvr32 /s CSEShellNsExt.dll
Ahhh, sorry I guess I didn't catch that. When I create a batch file with that code it hangs just like it does when running from the original location.
Do you have UAC turned off?
Are you on an admin account or on the Administrator (built in) account?