private
    { Private declarations }
    procedure WMQueryEndSession(var Msg: TWMQueryEndSession); message WM_QueryEndSession;

{...}

procedure TForm1.WMQueryEndSession
      (var Msg : TWMQueryEndSession) ;
begin
if MessageBox(Form1.Handle,PChar('Windows is attempting to shut down.  Allow the shutdown?'),PChar('Windows wants to shut down'),MB_YESNO) = mrYes then
   Msg.Result := 1
else
   Msg.Result := 0;
end;


DisplayName Process Idle Tasks
WinVers XP|vista|win7|win8orgreater
Purpose Optimization
Action ShellExecuteAndWait rundll32 advapi32.dll,ProcessIdleTasks
Description This tool performs the following command:
Description
Description rundll32.exe advapi32.dll,ProcessIdleTasks
Description
Description Note: Microsoft BootVis forces ProcessIdleTasks to run before it profiles your system, which is why people think BootVis optimizes your system's boot speed (BootVis itself does not optimize your system at all).
Description
Description From MSDN:
Description "The file placement optimization, which is done no more often than once every three days, is an example of a task that is carried out when the system is deemed to be idle.
Description System Restore and other features of Windows XP also attempt to defer some work until the system is deemed to be idle. There are also some done-once-after-setup work items that also operate under the Idle Task Scheduling mechanisms.
Description All of these "idle tasks" are controllable by a system API in advapi32.dll: ProcessIdleTasks.
Description The API's sole purpose is to allow benchmarks a simple way to force any pending idle tasks to be executed immediately, without having to wait a lengthy period of time."
Description
Description As you can see from the MSDN blurb, there are many things that can fall under 'idle tasks' which will be executed when you run this tool. It can take quite a long time to run if your system has a lot of pending tasks.


This is the procedure I followed when cleaning up after an ill-behaved 32-bit development tool that apparently wasn't aware that any of its users might possibly be needing a 64-bit OS. (DOH!)

All the warnings and caveats in the post still apply. About the only things that need to be noted for Vista and later are UAC (of course) and to check whether the filter driver is 64-bit if you're on a 64-bit Windows if it exists on the filesystem. (The post indicates that you should proceed if the filter driver does not exist on the filesystem.) Of course, a 32-bit filter will break a 64-bit driver. :) (How to check this is beyond the scope of a blog comment. Especially when the entry was aimed at technicians.)

1. Just uninstall divx
2. uninstall and all codecs.

t===he divx codec in the divx package corrupts the codecs and vista can’t read it after corrupting it==

3. reinstall codecs but not the one from divx.

!!!!!but don’t use an divx codecs!!!!!

just install the divx PLAYER Only!
====Don’t install the divx codec when installing divx player ==

NO divx codec the problem is the divx codec not compatible or conflicting with windows vista. i wouldnt recommend going to system as changing settings it is dangerous