Vista logon changes Dual monitor display settings
Posted by admin on Jul 31st, 2006
I use an external monitor with my laptop for a dual monitor extended desktop. I want the external monitor to be the primary. This is easily setup via my video driver software, windows display settings, or third party SW like UltrMon. The problem is at logon Windows Vista resets the display settings to make the Laptop screen the primary display, and changes the "layout" of the monitor locations, and sometimes the refresh rate of the external monitor. This happens at any logon whether from system restart or a simple logon from locking the system. I experimented with UltraMon to see if simply forcing the display settings I want via the StartUp menu would work. It appears the change Vista causes happens after the services and StartUp programs load. This seems consistent with the fact that a simple unlock logon causes the same problem.Note: the reset occurs at the end of the logon sequence. The logon screen itself is always positioned correctly, and the desktop is redrawn properly on both monitors until the end of the sequence when the display is changed.System Info: Dell XPS M1212 Laptop, NVidia Ge Force Go 7400 Adapter, Dell 2007WFP external Monitor, Windows Vista Home Premium Upgrade, all latest drivers from Dell and MS, clean system (only OEM as delivered software with a by the book upgrade to Vista), software passed vista compatibility checks.
Aug 5th, 2006 at 12:31 am
I think I solved my own problem. After a second pass at selectively enabling each service, I found that disabling "Windows Event Log" solved the problem... at least for now.Right click the Computer Icon, select Manage, open Services and Applications, open the Services snap in, find "Windows Event Log", right click "Windows Event Log", select Properties, in the dialog select Disable. The restart.Hope this helps others"sgk00" wrote:
Aug 7th, 2006 at 02:33 am
On Mar 22, 1:53 am, sgk00 wrote: Found a different solution that I wanted to pass on. For me, Nvidia has a control panel that allows you to change the monitor configuration. It appears that Windows and NVidia were fighting over control, and Nvidia was winning. So, I stopped changing the dual monitor settings in Windows starting changing them in Nvidia, and my problems went away.HTH!
Aug 12th, 2006 at 03:29 am
I too was having the same problem with my laptop and an external monitor. Whenever I logged in, my display settings would get all get reset. I tried disabling the Windows event log as suggested and that corrected the monitor issue, but had some other unintended consequences. By disabling the event log, the Windows Task Scheduler also becomes disabled, thus any applications dependent on the Task Scheduler won't run. After further research I found the root cause of the dual monitor problem. There is a task in the task scheduler called TMM (Microsoft Transient MultiMonitor Manager). I disabled this task, and all seems to work fine now. Hope this helps others.Thomas Thomas51 Thomas51's Profile: forums.techarena.in/member.php?userid=24828 View this thread: forums.techarena.in/showthread.php?t=708148forums.techarena.in
Aug 17th, 2006 at 04:17 am
Disabling TMM worked for me too, thanks a million!But when TMM was off, it wouldn't detect if I had one plugged in when I logged in or came out of sleep, which was helpful. So I came up with a few modified settings of the TMM task. Basically, it tells TMM to run at logon and when coming out of sleep, but to turn off after a minute so it won't be active during lock or unlocks. I still have to rearange every morning though. Here it is.<?xml version="1.0" encoding="UTF16"?> <Task version="1.2" xmlns="schemas.microsoft.com/windows/2004/02/mit/task"> <RegistrationInfo> <Source>MobilePC Display Handling</Source> <Author>Microsoft Corporation</Author> <Description>Microsoft Transient MultiMonitor Manager</Description> <URI>Microsoft\Windows\MobilePC\TMM</URI> <SecurityDescriptor>D:(A;;FA;;;BA)(A;;FA;;;SY)(A;;FR;;;AU)</SecurityDescriptor> </RegistrationInfo> <Triggers> <LogonTrigger id="0023ede20e7c42ceac3a9872e974d53f"> <ExecutionTimeLimit>PT1M</ExecutionTimeLimit> <Enabled>true</Enabled> <Delay>PT2S</Delay> </LogonTrigger> <EventTrigger id="b79242a8a65d434da58ada06a95fa5d1"> <ExecutionTimeLimit>PT1M</ExecutionTimeLimit> <Enabled>true</Enabled> <Subscription><QueryList><Query Id="0" Path="System"><Select Path="System">*[System[Provider[@Name='MicrosoftWindowsPowerTroubleshooter'] and EventID=1]]</Select></Query></QueryList></Subscription> <Delay>PT2S</Delay> </EventTrigger> </Triggers> <Principals> <Principal id="Users"> <GroupId>Authenticated Users</GroupId> <RunLevel>LeastPrivilege</RunLevel> </Principal> </Principals> <Settings> <IdleSettings> <Duration>PT10M</Duration> <WaitTimeout>PT1H</WaitTimeout> <StopOnIdleEnd>false</StopOnIdleEnd> <RestartOnIdle>false</RestartOnIdle> </IdleSettings> <MultipleInstancesPolicy>Parallel</MultipleInstancesPolicy> <DisallowStartIfOnBatteries>false</DisallowStartIfOnBatteries> <StopIfGoingOnBatteries>false</StopIfGoingOnBatteries> <AllowHardTerminate>true</AllowHardTerminate> <StartWhenAvailable>true</StartWhenAvailable> <RunOnlyIfNetworkAvailable>false</RunOnlyIfNetworkAvailable> <AllowStartOnDemand>true</AllowStartOnDemand> <Enabled>true</Enabled> <Hidden>false</Hidden> <RunOnlyIfIdle>false</RunOnlyIfIdle> <WakeToRun>false</WakeToRun> <ExecutionTimeLimit>PT1M</ExecutionTimeLimit> <Priority>7</Priority> </Settings> <Actions Context="Users"> <ComHandler> <ClassId>{35EF4182F9004632B0728639E4478A61}</ClassId> </ComHandler> </Actions> </Task>"Thomas51" wrote: