RE: Repeatable HKU/SID_CLASSES Corruption after Unattend.Txt XPSP1 Ins

Update to the problem:

The same problem exists in HKCU\Software\Classes. In other words, showing
permissions on HKCU\Software\Classes shows the same unknown SID number.




"hunt01@xxxxxxxxxxxxxxxx" wrote:

> I've got a repeatable issue with XP (SP1) Unattend.txt install. Here's what
> happens:
>
> 1. WinPE PXE boots, formats the drives, kick off unattend.txt.
> 2. Unattend.txt puts XP SP1 onto the box, then runs the guirunonce bit to
> install 70MB or so of hotfixes, SMS SP1, and Novell client.
> 3. After bootup, SMS then starts installing applications.
>
> Somewhere in this process, HKU\(currently-logged-in-SID)_CLASSES\ key
> develops a problem - users have no rights to that key. The net effect is
> that normal users cannot change file associations. If I go to permissions on
> that key, administrators, restricted, and system have normal rights, and
> there's a long SID in there (S-1-5-21-299502267-84292546-725345534-1007) that
> doesn't resolve to a name.
>
> If I remotely connect to the machine as an admin with regedt32, *ensure the
> problematic user is logged in* and change permissions for that key (say, add
> machinename\USERS full rights) then everything is fine, and that *one user*
> can then change file associations at will - including now and after a reboot.
>
> However, any other users that log into the box will have the same problem -
> they can't change file assocations until I perform the above fix.
>
> This is repeatable on 100% of the various computer types around.
>
> So, two desired solutions here:
>
> 1. How can I find out where in my imaging process this is happening? If I
> remove the GUIRUNONCE bit so no (hotfix|sms|novell) files install, the
> problem doesn't happen, but if I then (immediately after that first reboot)
> manually kick off the guirunonce script, the problem *still* doesn't happen,
> so it seems like it's either a contention issue or something else. :(
>
> 2. If I can't stop it from happening during the build, how do I fix it
> (allow all users to change file associations)? My current fix only fixes
> that ONE currently logged in user on that ONE box he's logged into. I'm
> content with a per-machine solution, but I'm hoping for a fix for all users
> on a given machine, rather than just one as my current fix allows.
>
> Any ideas on this one?
.

Relevant Pages

  • XP: Repeatable file associations problems after imaging PCs
    ... I've got a repeatable issue with XP Unattend.txt install. ... WinPE PXE boots, formats the drives, kick off unattend.txt. ... can then change file associations at will - including now and after a reboot. ... If I can't stop it from happening during the build, how do I fix it ...
    (microsoft.public.win2000.registry)
  • Repeatable problem with registry lockdown on 2 keys
    ... I've got a repeatable issue with XP (SP1) Unattend.txt install. ... can then change file associations at will - including now and after a reboot. ... If I can't stop it from happening during the build, how do I fix it ...
    (microsoft.public.windowsxp.perform_maintain)
  • Repeatable HKU/SID_CLASSES Corruption after Unattend.Txt XPSP1 Ins
    ... I've got a repeatable issue with XP (SP1) Unattend.txt install. ... can then change file associations at will - including now and after a reboot. ... If I can't stop it from happening during the build, how do I fix it ...
    (microsoft.public.windowsxp.setup_deployment)
  • Re: DHCP Client Service cannot start after conficker invaded
    ... Modify the permissions of this registry key: ... Have these permissions applied down the hive from the Parameters key ... I just registered to thanks you and to let you know this above fix the ... Another solution is to install SP2 - this fix the ...
    (microsoft.public.windows.server.general)
  • RE: Internal Error 2755 caused by Windows Installer
    ... Change the permissions on the windows folder to everyone. ... When I try to install a program, ... So there IS a fix, ...
    (microsoft.public.windowsxp.general)
Loading