Mydefrag does not start

[Darlis]

Could this be why when i run MyDefrag the "PreventPowerSaving(yes)" and PreventScreenSaving(yes) did not work from Settings script, but work if i put them in the Fastupdate or SlowOptimise script?

If you have no "RunScript("Settings")", or better "RunScript("Settings.MyD")" in your scripts, then the settings are not processed. You can also add the "Debug(447)" statement an take a look in the debug log, if the Settings.MyD is processed.

[jeroen]

Could this be why when i run MyDefrag the "PreventPowerSaving(yes)" and PreventScreenSaving(yes) did not work from Settings script?

No. The problem discussed here will cause MyDefrag not to do anything and immediately finish.

[korinor]

Hi,

I downloaded MyDefrag v4.1.2 few minutes ago, but it doesn't start. It's like the first posts in this thread, there is absolutely happening at all. Providing the "-d 6" option doesn't bring up a logfile, other changes discussed her like "Settings.MyD instead of Settings" are already stored in the script files.

There is already JKDefrag along with JKDefragGUI installed (under C:\Programme\JKDefrag, and I installed MyDefrag into "C:\Programme\MyDefrag\". I already tried to uninstall and reinstall in the default given folder called "C:\Programme\MyDefrag v4.1.2\" but it doesn't help.

I've attached a filemon log in which you can see that MyDefrag is called via Explorer.exe. Explorer.exe is searching some kind of ADS, but I think this should not the problem? After this, mydefrag.exe itself searches some components, but it seems to end up in win.ini, I'm not sure. Regmon didn't show up any activity from MyDefrag.

I'm running avast! Home Edition 4.8 and Sunbelt Personal Firewall which don't show up any message or log entries. I disabled them and tried again, even with "-d 6" option, but no reaction.

I also tried it in a virtual machine running unter VirtualBox, here it worked. They both run under Windows XP Pro SP2, my computer is a Intel P4 HT with 2 GB RAM and 160 GB hard disc containing 3 NTFS partitions, additionaly 2 linux partitions. JKDefrag never complained about this so I think MyDefrag would do either. The only visible difference to me is that the virtual machine doesn't run with Sunbelt PFW, it uses an old Kerio PFW 2.1.5. But the avast! is the same.

I'm amazed about the scripting feature of MyDefrag and wanted to try. An installation of 4.1.1 throw up the same, simply nothing.

Did you find out in the meantime what makes this happen? I'm seeing myself forced to test to uninstall Sunbelt PFW, with older versions I had some similar "bugs" like silent "not-execution" of old 16-bit-programs.

One final question, I didn't find an answer about it: Does MyDefrag require .net v3? I have only installed .net v1 and v2 so far.

Feel free to ask if I should provide more information.

Greetings,
korinor

[jeroen]

I've attached a filemon log in which you can see that MyDefrag is called via Explorer.exe. Explorer.exe is searching some kind of ADS, but I think this should not the problem? After this, mydefrag.exe itself searches some components, but it seems to end up in win.ini, I'm not sure. Regmon didn't show up any activity from MyDefrag.

Thanks for the filemon logfile, I appreciate it. It's a pity it does not show what is going wrong. What do you mean with "ADS"? After loading the executable Windows will load some system DLL's, it's not MyDefrag that is doing that.

Did you find out in the meantime what makes this happen?

No, and I am dying to know.

One final question, I didn't find an answer about it: Does MyDefrag require .net v3?

No, it does not use .net at all.

[Darlis]

ADS: Alternate data stream. You can attach information to files with this feature of NTFS. Such files are accessed with the ":" separator: MyDefrag.exe:Raec25ph4sudbf0hAaq5ehw3Nf:$DATA (:$DATA is optional)
Perhaps you have already heard something about "Zone.Identifier"?

[jeroen]

ADS: Alternate data stream.

Ok. I know what streams are, but your abbreviation did not ring a bell.

Perhaps you have already heard something about "Zone.Identifier"?

I'm not sure what you are asking. I see on the internet that they have something to do with security, but apart from that I don't know anything about them.

[Darlis]

The Zone.Identifier information is attached to all files, which have have been downloaded from the Internet. Thats why you get a security information, when you try to execute/install them.

This is the most common situation where ADS is (still) being used, thats why I mentioned it.

[jeroen]

Ok, thanks for the explanation. MyDefrag handles streams just like any other file.

[korinor]

No, it does not use .net at all.

I'm glad to hear this. I recently tested some other software which required .net 3. I didn't read it and the program did not show up any message about it.

Here is a log created from a profile run with the Dependency walker. I didn't think that it's necessary to check, but I tried.

Code:

Started "MYDEFRAG.EXE" (process 0x7B8) at address 0x00400000.  Successfully hooked module.
Loaded "NTDLL.DLL" at address 0x7C910000.  Successfully hooked module.
Loaded "KERNEL32.DLL" at address 0x7C800000.  Successfully hooked module.
DllMain(0x7C910000, DLL_PROCESS_ATTACH, 0x00000000) in "NTDLL.DLL" called.
DllMain(0x7C910000, DLL_PROCESS_ATTACH, 0x00000000) in "NTDLL.DLL" returned 1 (0x1).
DllMain(0x7C800000, DLL_PROCESS_ATTACH, 0x00000000) in "KERNEL32.DLL" called.
DllMain(0x7C800000, DLL_PROCESS_ATTACH, 0x00000000) in "KERNEL32.DLL" returned 1 (0x1).
Injected "DEPENDS.DLL" at address 0x08370000.
DllMain(0x08370000, DLL_PROCESS_ATTACH, 0x00000000) in "DEPENDS.DLL" called.
DllMain(0x08370000, DLL_PROCESS_ATTACH, 0x00000000) in "DEPENDS.DLL" returned 1 (0x1).
Loaded "ADVAPI32.DLL" at address 0x77DA0000.  Successfully hooked module.
Loaded "RPCRT4.DLL" at address 0x77E50000.  Successfully hooked module.
Loaded "SECUR32.DLL" at address 0x77FC0000.  Successfully hooked module.
Loaded "USER32.DLL" at address 0x7E360000.  Successfully hooked module.
Loaded "GDI32.DLL" at address 0x77EF0000.  Successfully hooked module.
Loaded "SHELL32.DLL" at address 0x7E670000.  Successfully hooked module.
Loaded "MSVCRT.DLL" at address 0x77BE0000.  Successfully hooked module.
Loaded "SHLWAPI.DLL" at address 0x77F40000.  Successfully hooked module.
Loaded "POWRPROF.DLL" at address 0x74A50000.  Successfully hooked module.
Loaded "DBGHELP.DLL" at address 0x59DD0000.  Successfully hooked module.
Loaded "VERSION.DLL" at address 0x77BD0000.  Successfully hooked module.
Entrypoint reached. All implicit modules have been loaded.
DllMain(0x77FC0000, DLL_PROCESS_ATTACH, 0x0012FD30) in "SECUR32.DLL" called.
DllMain(0x77FC0000, DLL_PROCESS_ATTACH, 0x0012FD30) in "SECUR32.DLL" returned 1 (0x1).
DllMain(0x77E50000, DLL_PROCESS_ATTACH, 0x0012FD30) in "RPCRT4.DLL" called.
DllMain(0x77E50000, DLL_PROCESS_ATTACH, 0x0012FD30) in "RPCRT4.DLL" returned 1 (0x1).
DllMain(0x77DA0000, DLL_PROCESS_ATTACH, 0x0012FD30) in "ADVAPI32.DLL" called.
DllMain(0x77DA0000, DLL_PROCESS_ATTACH, 0x0012FD30) in "ADVAPI32.DLL" returned 1 (0x1).
DllMain(0x77EF0000, DLL_PROCESS_ATTACH, 0x0012FD30) in "GDI32.DLL" called.
DllMain(0x77EF0000, DLL_PROCESS_ATTACH, 0x0012FD30) in "GDI32.DLL" returned 1 (0x1).
DllMain(0x7E360000, DLL_PROCESS_ATTACH, 0x0012FD30) in "USER32.DLL" called.
LoadLibraryW("C:\WINDOWS\system32\IMM32.DLL") called from "USER32.DLL" at address 0x7E39DD59.
Loaded "IMM32.DLL" at address 0x76330000.  Successfully hooked module.
DllMain(0x76330000, DLL_PROCESS_ATTACH, 0x00000000) in "IMM32.DLL" called.
GetProcAddress(0x76330000 [IMM32.DLL], "ImmWINNLSEnableIME") called from "USER32.DLL" at address 0x7E38D43E and returned 0x7633E699.
GetProcAddress(0x76330000 [IMM32.DLL], "ImmWINNLSGetEnableStatus") called from "USER32.DLL" at address 0x7E38D453 and returned 0x7633E6C0.
GetProcAddress(0x76330000 [IMM32.DLL], "ImmSendIMEMessageExW") called from "USER32.DLL" at address 0x7E38D468 and returned 0x7633EB54.
GetProcAddress(0x76330000 [IMM32.DLL], "ImmSendIMEMessageExA") called from "USER32.DLL" at address 0x7E38D47D and returned 0x7633EB6F.
GetProcAddress(0x76330000 [IMM32.DLL], "ImmIMPGetIMEW") called from "USER32.DLL" at address 0x7E38D492 and returned 0x7633E789.
GetProcAddress(0x76330000 [IMM32.DLL], "ImmIMPGetIMEA") called from "USER32.DLL" at address 0x7E38D4A7 and returned 0x7633E7BD.
GetProcAddress(0x76330000 [IMM32.DLL], "ImmIMPQueryIMEW") called from "USER32.DLL" at address 0x7E38D4BC and returned 0x7633E824.
GetProcAddress(0x76330000 [IMM32.DLL], "ImmIMPQueryIMEA") called from "USER32.DLL" at address 0x7E38D4D1 and returned 0x7633E92C.
GetProcAddress(0x76330000 [IMM32.DLL], "ImmIMPSetIMEW") called from "USER32.DLL" at address 0x7E38D4E6 and returned 0x7633E9B5.
GetProcAddress(0x76330000 [IMM32.DLL], "ImmIMPSetIMEA") called from "USER32.DLL" at address 0x7E38D4FB and returned 0x7633EAD9.
GetProcAddress(0x76330000 [IMM32.DLL], "ImmAssociateContext") called from "USER32.DLL" at address 0x7E38D510 and returned 0x763323BF.
GetProcAddress(0x76330000 [IMM32.DLL], "ImmEscapeA") called from "USER32.DLL" at address 0x7E38D525 and returned 0x76337C45.
GetProcAddress(0x76330000 [IMM32.DLL], "ImmEscapeW") called from "USER32.DLL" at address 0x7E38D53A and returned 0x76337EC1.
GetProcAddress(0x76330000 [IMM32.DLL], "ImmGetCompositionStringA") called from "USER32.DLL" at address 0x7E38D54F and returned 0x76335B82.
GetProcAddress(0x76330000 [IMM32.DLL], "ImmGetCompositionStringW") called from "USER32.DLL" at address 0x7E38D564 and returned 0x763354AA.
GetProcAddress(0x76330000 [IMM32.DLL], "ImmGetCompositionWindow") called from "USER32.DLL" at address 0x7E38D579 and returned 0x76333B68.
GetProcAddress(0x76330000 [IMM32.DLL], "ImmGetContext") called from "USER32.DLL" at address 0x7E38D58E and returned 0x763322B3.
GetProcAddress(0x76330000 [IMM32.DLL], "ImmGetDefaultIMEWnd") called from "USER32.DLL" at address 0x7E38D5A3 and returned 0x763397DE.
GetProcAddress(0x76330000 [IMM32.DLL], "ImmIsIME") called from "USER32.DLL" at address 0x7E38D5B8 and returned 0x76338C74.
GetProcAddress(0x76330000 [IMM32.DLL], "ImmReleaseContext") called from "USER32.DLL" at address 0x7E38D5CD and returned 0x763329F3.
GetProcAddress(0x76330000 [IMM32.DLL], "ImmRegisterClient") called from "USER32.DLL" at address 0x7E38D5E2 and returned 0x763322FA.
GetProcAddress(0x76330000 [IMM32.DLL], "ImmGetCompositionFontW") called from "USER32.DLL" at address 0x7E38D5F7 and returned 0x76334849.
GetProcAddress(0x76330000 [IMM32.DLL], "ImmGetCompositionFontA") called from "USER32.DLL" at address 0x7E38D60C and returned 0x763347B1.
GetProcAddress(0x76330000 [IMM32.DLL], "ImmSetCompositionFontW") called from "USER32.DLL" at address 0x7E38D621 and returned 0x763349EE.
GetProcAddress(0x76330000 [IMM32.DLL], "ImmSetCompositionFontA") called from "USER32.DLL" at address 0x7E38D636 and returned 0x763348E1.
GetProcAddress(0x76330000 [IMM32.DLL], "ImmSetCompositionWindow") called from "USER32.DLL" at address 0x7E38D64B and returned 0x76334DF6.
GetProcAddress(0x76330000 [IMM32.DLL], "ImmNotifyIME") called from "USER32.DLL" at address 0x7E38D660 and returned 0x76336FF8.
GetProcAddress(0x76330000 [IMM32.DLL], "ImmLockIMC") called from "USER32.DLL" at address 0x7E38D675 and returned 0x76339F4D.
GetProcAddress(0x76330000 [IMM32.DLL], "ImmUnlockIMC") called from "USER32.DLL" at address 0x7E38D68A and returned 0x76339F65.
GetProcAddress(0x76330000 [IMM32.DLL], "ImmLoadIME") called from "USER32.DLL" at address 0x7E38D69F and returned 0x7633778F.
GetProcAddress(0x76330000 [IMM32.DLL], "ImmSetOpenStatus") called from "USER32.DLL" at address 0x7E38D6B4 and returned 0x7633472B.
GetProcAddress(0x76330000 [IMM32.DLL], "ImmFreeLayout") called from "USER32.DLL" at address 0x7E38D6C9 and returned 0x76336E63.
GetProcAddress(0x76330000 [IMM32.DLL], "ImmActivateLayout") called from "USER32.DLL" at address 0x7E38D6DE and returned 0x763377ED.
GetProcAddress(0x76330000 [IMM32.DLL], "ImmGetCandidateWindow") called from "USER32.DLL" at address 0x7E38D6F3 and returned 0x76333BB3.
GetProcAddress(0x76330000 [IMM32.DLL], "ImmSetCandidateWindow") called from "USER32.DLL" at address 0x7E38D708 and returned 0x76334E74.
GetProcAddress(0x76330000 [IMM32.DLL], "ImmConfigureIMEW") called from "USER32.DLL" at address 0x7E38D71D and returned 0x76337A9B.
GetProcAddress(0x76330000 [IMM32.DLL], "ImmGetConversionStatus") called from "USER32.DLL" at address 0x7E38D732 and returned 0x76333AA6.
GetProcAddress(0x76330000 [IMM32.DLL], "ImmSetConversionStatus") called from "USER32.DLL" at address 0x7E38D747 and returned 0x76334617.
GetProcAddress(0x76330000 [IMM32.DLL], "ImmSetStatusWindowPos") called from "USER32.DLL" at address 0x7E38D75C and returned 0x76334D8E.
GetProcAddress(0x76330000 [IMM32.DLL], "ImmGetImeInfoEx") called from "USER32.DLL" at address 0x7E38D771 and returned 0x76339C9F.
GetProcAddress(0x76330000 [IMM32.DLL], "ImmLockImeDpi") called from "USER32.DLL" at address 0x7E38D786 and returned 0x76339BCC.
GetProcAddress(0x76330000 [IMM32.DLL], "ImmUnlockImeDpi") called from "USER32.DLL" at address 0x7E38D79B and returned 0x76339C1C.
GetProcAddress(0x76330000 [IMM32.DLL], "ImmGetOpenStatus") called from "USER32.DLL" at address 0x7E38D7B0 and returned 0x76333AE3.
GetProcAddress(0x76330000 [IMM32.DLL], "ImmSetActiveContext") called from "USER32.DLL" at address 0x7E38D7C5 and returned 0x763329FE.
GetProcAddress(0x76330000 [IMM32.DLL], "ImmTranslateMessage") called from "USER32.DLL" at address 0x7E38D7DA and returned 0x7633DE85.
GetProcAddress(0x76330000 [IMM32.DLL], "ImmLoadLayout") called from "USER32.DLL" at address 0x7E38D7EF and returned 0x76338739.
GetProcAddress(0x76330000 [IMM32.DLL], "ImmProcessKey") called from "USER32.DLL" at address 0x7E38D804 and returned 0x7633E0F3.
GetProcAddress(0x76330000 [IMM32.DLL], "ImmPutImeMenuItemsIntoMappedFile") called from "USER32.DLL" at address 0x7E38D819 and returned 0x76342E24.
GetProcAddress(0x76330000 [IMM32.DLL], "ImmGetProperty") called from "USER32.DLL" at address 0x7E38D82E and returned 0x76338BAE.
GetProcAddress(0x76330000 [IMM32.DLL], "ImmSetCompositionStringA") called from "USER32.DLL" at address 0x7E38D843 and returned 0x763367F5.
GetProcAddress(0x76330000 [IMM32.DLL], "ImmSetCompositionStringW") called from "USER32.DLL" at address 0x7E38D858 and returned 0x7633681C.
GetProcAddress(0x76330000 [IMM32.DLL], "ImmEnumInputContext") called from "USER32.DLL" at address 0x7E38D86D and returned 0x763337EA.
GetProcAddress(0x76330000 [IMM32.DLL], "ImmSystemHandler") called from "USER32.DLL" at address 0x7E38D882 and returned 0x76339D94.
GetProcAddress(0x76330000 [IMM32.DLL], "CtfImmTIMActivate") called from "USER32.DLL" at address 0x7E38D897 and returned 0x76343F2B.
GetProcAddress(0x76330000 [IMM32.DLL], "CtfImmRestoreToolbarWnd") called from "USER32.DLL" at address 0x7E38D8AC and returned 0x763434FA.
GetProcAddress(0x76330000 [IMM32.DLL], "CtfImmHideToolbarWnd") called from "USER32.DLL" at address 0x7E38D8C1 and returned 0x76343531.
GetProcAddress(0x76330000 [IMM32.DLL], "CtfImmDispatchDefImeMessage") called from "USER32.DLL" at address 0x7E38D8D6 and returned 0x76344324.
DllMain(0x76330000, DLL_PROCESS_ATTACH, 0x00000000) in "IMM32.DLL" returned 1 (0x1).
LoadLibraryW("C:\WINDOWS\system32\IMM32.DLL") returned 0x76330000.
DllMain(0x7E360000, DLL_PROCESS_ATTACH, 0x0012FD30) in "USER32.DLL" returned 1 (0x1).
DllMain(0x77BE0000, DLL_PROCESS_ATTACH, 0x0012FD30) in "MSVCRT.DLL" called.
GetProcAddress(0x7C800000 [KERNEL32.DLL], "InitializeCriticalSectionAndSpinCount") called from "MSVCRT.DLL" at address 0x77C079C2 and returned 0x7C80B839.
DllMain(0x77BE0000, DLL_PROCESS_ATTACH, 0x0012FD30) in "MSVCRT.DLL" returned 1 (0x1).
DllMain(0x77F40000, DLL_PROCESS_ATTACH, 0x0012FD30) in "SHLWAPI.DLL" called.
GetProcAddress(0x7C800000 [KERNEL32.DLL], "CreateTimerQueue") called from "SHLWAPI.DLL" at address 0x77F45BF1 and returned 0x7C82BFE6.
GetProcAddress(0x7C800000 [KERNEL32.DLL], "DeleteTimerQueue") called from "SHLWAPI.DLL" at address 0x77F45C00 and returned 0x7C862FAB.
GetProcAddress(0x7C800000 [KERNEL32.DLL], "CreateTimerQueueTimer") called from "SHLWAPI.DLL" at address 0x77F45C0F and returned 0x7C82118D.
GetProcAddress(0x7C800000 [KERNEL32.DLL], "ChangeTimerQueueTimer") called from "SHLWAPI.DLL" at address 0x77F45C1F and returned 0x7C812733.
GetProcAddress(0x7C800000 [KERNEL32.DLL], "DeleteTimerQueueTimer") called from "SHLWAPI.DLL" at address 0x77F45C2D and returned 0x7C821140.
DllMain(0x77F40000, DLL_PROCESS_ATTACH, 0x0012FD30) in "SHLWAPI.DLL" returned 1 (0x1).
DllMain(0x7E670000, DLL_PROCESS_ATTACH, 0x0012FD30) in "SHELL32.DLL" called.
GetProcAddress(0x7C800000 [KERNEL32.DLL], "CreateActCtxW") called from "SHELL32.DLL" at address 0x7E6D76CE and returned 0x7C81546C.
GetProcAddress(0x7C800000 [KERNEL32.DLL], "ActivateActCtx") called from "SHELL32.DLL" at address 0x7E697529 and returned 0x7C80A654.
LoadLibraryW("comctl32.dll") called from "SHELL32.DLL" at address 0x7E6D7304.
Loaded "COMCTL32.DLL" at address 0x773A0000.  Successfully hooked module.
DllMain(0x773A0000, DLL_PROCESS_ATTACH, 0x00000000) in "COMCTL32.DLL" called.
GetProcAddress(0x7C800000 [KERNEL32.DLL], "GetSystemWindowsDirectoryW") called from "COMCTL32.DLL" at address 0x7742B739 and returned 0x7C80AD39.
GetProcAddress(0x7C800000 [KERNEL32.DLL], "CreateActCtxW") called from "COMCTL32.DLL" at address 0x7742B5BC and returned 0x7C81546C.
LoadLibraryA("imagehlp.dll") called from "ADVAPI32.DLL" at address 0x77E0C90D.
Loaded "IMAGEHLP.DLL" at address 0x76C50000.  Successfully hooked module.
DllMain(0x76C50000, DLL_PROCESS_ATTACH, 0x00000000) in "IMAGEHLP.DLL" called.
DllMain(0x76C50000, DLL_PROCESS_ATTACH, 0x00000000) in "IMAGEHLP.DLL" returned 1 (0x1).
LoadLibraryA("imagehlp.dll") returned 0x76C50000.
GetProcAddress(0x76C50000 [IMAGEHLP.DLL], "SymInitialize") called from "ADVAPI32.DLL" at address 0x77E0C926 and returned 0x76C5AE02.
GetProcAddress(0x76C50000 [IMAGEHLP.DLL], "SymCleanup") called from "ADVAPI32.DLL" at address 0x77E0C940 and returned 0x76C5A9BE.
GetProcAddress(0x76C50000 [IMAGEHLP.DLL], "StackWalk") called from "ADVAPI32.DLL" at address 0x77E0C956 and returned 0x76C5A9A4.
GetProcAddress(0x76C50000 [IMAGEHLP.DLL], "SymGetSymFromAddr") called from "ADVAPI32.DLL" at address 0x77E0C96C and returned 0x76C5AD18.
GetProcAddress(0x76C50000 [IMAGEHLP.DLL], "SymFunctionTableAccess") called from "ADVAPI32.DLL" at address 0x77E0C982 and returned 0x76C5AB44.
GetProcAddress(0x76C50000 [IMAGEHLP.DLL], "SymGetModuleBase") called from "ADVAPI32.DLL" at address 0x77E0C998 and returned 0x76C5AC48.
GetProcAddress(0x59DD0000 [DBGHELP.DLL], "SymInitialize") called from "IMAGEHLP.DLL" at address 0x76C57368 and returned 0x59DED6FB.
GetProcAddress(0x59DD0000 [DBGHELP.DLL], "StackWalk") called from "IMAGEHLP.DLL" at address 0x76C57368 and returned 0x59DF334C.
Second chance exception 0xC0000005 (Access Violation) occurred in "ADVAPI32.DLL" at address 0x77E0CC33.
Exited "MYDEFRAG.EXE" (process 0x7B8) with code -1073741819 (0xC0000005).

As you can see in the last line before "Exiting" there is an error in combination with the ADVAPI32.DLL. It's the version 5.1.2600.3520. On my virtual machine MyDefrag is running without any problem, here it's an older version (5.1.2600.2180).

I don't know if there is an separate update for this DLL, currently I have SP2 installed. I'm planning to update to SP3 when there is some more time

But maybe the above log helps?

[jeroen]

Thanks for the logfile, I appreciate it. Everything after the line about "CreateActCtxW" has to to with MyDefrag trying to write to it's debug logfile. I don't know what the "CreateActCtxW" system call does exactly, I don't use it in MyDefrag and I think this is probably Windows still initializing for the program. According to the Microsoft manual it has something to do with manifests. Which is very strange, if there is something wrong with the manifest then usually Windows will popup an error message.

[korinor]

Hi Jeroen,

thanks for your reply. Can you explain what these manifests are and what purpose they have? Maybe it can help me for searching a solution. My Windows installation is rather "old", it means the initial installation is about 5 years old. I installed only these programs which I really wanted to use, other testings went done in virtual machines. It's possible that my Windows installation is so highly modified in a particular way which will cause some programs to crash, maybe MyDefrag too. It may sound crazy, but in case of Windows everything seems possible. But I'm a freelancer who has currently very little time for a complete reinstallation, that's the reason why the SP3 installation is still on my todolist

I like programs like this which don't require other packages like .net or some other huge "crap". It makes my crazy indeed if a program won't work without telling what's wrong. In this case it seems that Windows somehow prevents it from telling. I checked the event log, but it doesn't contain anything related to MyDefrag.

Maybe I can test MyDefrag with a newly created user in the meantime.

[korinor]

Hi,

today I tested MyDefrag on my machine under a fresh created user. It's happening the same way. Therefore it's not a user relevant fault but a system relevant. Under my notebook running a AMD Sempron MyDefrag is running like a charm. It's funny because my notebook doesn't receive updates as often as my desktop computer. This is the only major difference I currently see. But I cannot believe this would be the cause.

Currently I don't know any further possibility to test why it won't run. I think I wait for the next version of MyDefrag to test.

[jeroen]

Thanks for testing, I appreciate it. It sounds like you have done everything possible. I wish I knew what was happening, but I have no idea. And since I don't know what is happening I cannot fix it, so the next release will very likely have the exact same problem.

[korinor]

Thanks for testing, I appreciate it. It sounds like you have done everything possible. I wish I knew what was happening, but I have no idea. And since I don't know what is happening I cannot fix it, so the next release will very likely have the exact same problem.

Hi Jeroen, thanks for your reply.

I know that you can't do anything about it as long as we don't find out about the fault. I'm not angry about you or MyDefrag. I think it's very likely that some kind of Windows update may cause this. My computer is most up-to-date but MyDefrag won't run. The virtual machine and the notebook aren't up-to-date and MyDefrag works. But there may be some other software too which may prevent MyDefrag from running. "Funny" that nobody else seems to have the same problem.

[usch]

Any hint in the XP event log, in the Application or System section?