tricky ENUM key
#1
Posted 16 May 2010 - 02:48 PM
I already tryed to change the permissions before i copy, to allow all, but to no avail.
If i build now a NaughtyPE on the other computer ENUM works fine on that computer, but not on the first one.
Does anyone know, what causes ENUM key to act up while no other keys do that?
btw. I'm loged in as admin on both machines. And if i want to view the permissions, the error message says something like, you do not have the rights to view the permissions but you can change them.
Which is just a lie as windows does not let me change the permissions.
#2
Posted 16 May 2010 - 03:18 PM
But a admin may grant permissions himself.
Take ownership of ENUM keys first.
Change permisssions next.
#4
Posted 16 May 2010 - 08:49 PM
How can some keys have this problems an others don't? They are all created by WB. Shouldn't that mean, that they are all created with the same permissions?
#5
Posted 16 May 2010 - 09:23 PM
Do you have some ENUM examples?How can some keys have this problems an others don't? They are all created by WB. Shouldn't that mean, that they are all created with the same permissions?
How do you add ENUM keys?
Do you add .reg files? Do you process .script files?
Did you used temp files from a previous build?
How does WB create ENUM keys?
Does WB use a windows api?
Does windows api set permission defaults to a local account?
Which permissions does exist at ENUM key?
@Sha0
At XP machines I prefer sc.exe to launch application at system account
%SystemRoot%\system32\sc.exe delete SystemCmd >nul %SystemRoot%\system32\sc.exe create SystemCmd binpath= "%SystemRoot%\system32\cmd.exe /c pushd %~dps0 & start Builder.exe" type= own type= interact >nul %SystemRoot%\system32\sc.exe start SystemCmd >nul %SystemRoot%\system32\sc.exe delete SystemCmd >nul
#6
Posted 16 May 2010 - 10:57 PM
All registry entries are added by scripts.Do you have some ENUM examples?
How do you add ENUM keys?
Do you add .reg files? Do you process .script files?
I used the temp-, the workplace-, and the target files from a previous build on a different machine.Did you used temp files from a previous build?
Just like any other, i would assume.How does WB create ENUM keys?
I guess so.Does WB use a windows api?
I assume as much, but if that's the problem, then it should be impossible to edit any hive on another machine and use it during boot on the original machine again. Shouldn't it?Does windows api set permission defaults to a local account?
I didn't check. I have come across a far bigger problem, which caused me to bin the whole update and if i don't do the update, i won't waste time on fixing potential bugs.Which permissions does exist at ENUM key?
#7
Posted 17 May 2010 - 06:07 PM
ControlSet001 get permission to group admin and user system, owner group admin.then it should be impossible to edit any hive on another machine and use it during boot on the original machine again. Shouldn't it?
ENUM is a special branch: default windows set special permissions
At WB permissions goes to current local user and user system, owner current local user.
At another machine a user with admin permission may open ControlSet001, but ENUM is protected.
A booted PE with system permission can open ENUM.
#8
Posted 17 May 2010 - 06:42 PM
#9
Posted 17 May 2010 - 08:03 PM
Or ask a WB developer to adjust WB.
No tested: copy permissions from ControlSet001 to ENUM.
Sunincal can do this:
Compare, slightly different conditions:
http://www.911cd.net...&...st&p=159987
http://www.911cd.net...showtopic=23424
#10
Posted 17 May 2010 - 08:37 PM
That's a very good idea. Will do that.Or ask a WB developer to adjust WB.
Thanks.
1 user(s) are reading this topic
0 members, 1 guests, 0 anonymous users