MS-Config

[Roger Fink]

I just unchecked a few items under the "Startup" and "Services" tabs of
MS-config.

Now, whenever I open it, whether I make a change or not, I get a message
after closing (unless I close by selecting "cancel") that I have to reboot
for the changes I made to System Configuration to take effect. I also get a
message after I reboot (or log off and log on) informing me that I have made
changes to the system configuration and to check the box if I don't want the
configuration utility to launch on reboot or see this message again (these
messages would be normal if I had made changes).

The items I unchecked in Startup were related to nVidia features and also
mobsync. The items I unchecked in services were Automatic Updates, Task
Scheduler, and Messenger, if any of that is relevant.

I rarely use MS-Config but I'd still like to get rid of this annoyance.

 

[Pegasus \(MVP\)]

I just unchecked a few items under the "Startup" and "Services" tabs of
MS-config.

Now, whenever I open it, whether I make a change or not, I get a message
after closing (unless I close by selecting "cancel") that I have to reboot
for the changes I made to System Configuration to take effect. I also get
a
message after I reboot (or log off and log on) informing me that I have
made
changes to the system configuration and to check the box if I don't want
the
configuration utility to launch on reboot or see this message again (these
messages would be normal if I had made changes).

The items I unchecked in Startup were related to nVidia features and also
mobsync. The items I unchecked in services were Automatic Updates, Task
Scheduler, and Messenger, if any of that is relevant.

I rarely use MS-Config but I'd still like to get rid of this annoyance.

When you see the msconfig message to check the box, you MUST
check the tick box to prevent this message from popping up again.

 

[Roger Fink]

When you see the msconfig message to check the box, you MUST
check the tick box to prevent this message from popping up again.

Yes, and I should have mentioned that I have been doing that.

 

[Pegasus \(MVP\)]

Yes, and I should have mentioned that I have been doing that.

Placing the tick mark is equivalent to deleting this registry value:
HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\Run\msconfig

which had the following data:
C:\WINDOWS\PCHealth\HelpCtr\Binaries\MSConfig.exe /auto

If placing the tick mark has no effect then your account has
insufficient privileges to delete the above registry value. You
can try deleting it manually or else you must fix the permission
structure for he RUN key.

 

[Roger Fink]

Placing the tick mark is equivalent to deleting this registry value:
HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\Run\msconfig

which had the following data:
C:\WINDOWS\PCHealth\HelpCtr\Binaries\MSConfig.exe /auto

If placing the tick mark has no effect then your account has
insufficient privileges to delete the above registry value. You
can try deleting it manually or else you must fix the permission
structure for he RUN key.

The tick mark does remove the registry value and thus prevents ms-config
from running automatically after boot-up. The problem is that if during a
session I elect to open ms-config, even if I don't make any changes to the
configuration closing it by hitting OK rather than Cancel will: a) cause
the option-to-reboot box to pop up, and b) after subsequent reboot the
warning box containing the tick mark option will pop up.

As a practical matter this is not too big a deal, since the problem can be
avoided by always closing via Cancel when you don't make any changes, but it
doesn't seem like normal behavior.