Boot and Shutdown tweak not applied

MSFN Forum: Boot and Shutdown tweak not applied - MSFN Forum

If you are having issues with Windows after removing components and have come to ask for help, please attach (not paste) your Last Session.ini file to your post to facilitate quicker assistance.

Page 1 of 1

You cannot start a new topic
You cannot reply to this topic

Boot and Shutdown tweak not applied Disable automatic restart on System Failure Rate Topic:

#1 m0rpheus

Group: Members
Posts: 7
Joined: 25-January 07

Posted 05 December 2007 - 10:53 AM

Happy nLite user here, but ....

I've notice that the "crash control" tweak (see below) doesn't get applied for some odd reason -- nLite v1.3 - 1.4.

- Send an administrative alert --> Disable
- Automatically restart --> Disable

- Write debugging information --> (none)

Corresponding (AddReg) registry entries 'present' in NLITE.INF:

[T]
.....
HKLM,"SYSTEM\CurrentControlSet\Control\CrashControl","CrashDumpEnabled",0x00010001,0
HKLM,"SYSTEM\CurrentControlSet\Control\CrashControl","AutoReboot",0x00010001,0
HKLM,"SYSTEM\CurrentControlSet\Control\CrashControl","SendAlert",0x00010001,0
HKLM,"SYSTEM\CurrentControlSet\Control\CrashControl","LogEvent",0x00010001,0
.....

The strange thing is, all other AddReg entries are processed AND applied, EXCEPT the entries listed here. Perhaps, Windows reverts these settings back to their defaults? This is no big deal, but it would be nice to have the settings applied 'permanently' so I don't have to manually change it. Anyone else?

TIA.

#2 mitsukai

Advanced Member

Group: Members
Posts: 476
Joined: 07-January 07

Posted 06 December 2007 - 01:54 PM

wondering same thing here

#3 platipus

Newbie

Group: Members
Posts: 16
Joined: 20-June 07

Posted 06 December 2007 - 09:25 PM

m0rpheus, on Dec 5 2007, 10:53 AM, said:

I've notice that the "crash control" tweak (see below) doesn't get applied for some odd reason -- nLite v1.3 - 1.4.

Anyone else?

Confirmed. Seems like a recurrent issue. Was present in several 1.3 betas, then gone in 1.3.5 final, re-appeared again in 1.4. My guess is that some combination of tweaks or removed componets triggers this.