Just now cannot file sync. The folder comparison goes smoothly then when it generates the page showing what will be deleted/updated/copied, it just sits there. Cancel button in top left is unresponsive. The Synchronize button in top right is grayed out. This began after upgrading to Windows 10. It worked a few times after the Windows 10 upgrade but no longer. It also started happening at the same time that the Windows 10 File Explorer started hanging. When File Explorer launches to This PC or Quick Access, it just sits there. If I hold down the start button and hit E, a new File Explorer window launches quickly and actually works. Am using Comodo Internet Security Premium.
Many thanks.
Program No Longer Working
- Posts: 5
- Joined: 9 Dec 2015
-
- Site Admin
- Posts: 7323
- Joined: 9 Dec 2007
You can send me a Process Explorer dump file at the time when FFS hangs and I'll have a closer look:
https://freefilesync.org/faq.php#crash
https://freefilesync.org/faq.php#crash
- Posts: 5
- Joined: 9 Dec 2015
I'll email it in a few minutes. It appears to only happen on some folders and not others. Also after it crashes, Windows 10 File Explorer no longer works properly. Very strange. Sorry about the size of the full dump, even compressed it's kind of big. I'll send a mini-dump of the original (larger) crash as well in case that helps. (Two different crashes.)
- Posts: 5
- Joined: 9 Dec 2015
System getting locked up, need to power off after crash. Getting "Explorer.exe System Call Failed" error.
- Posts: 5
- Joined: 9 Dec 2015
Came across this on bleepingcomputer regarding Windows 10 explorer crashes:
http://www.bleepingcomputer.com/forums/t/586464/windows-10-explorerexe-crashes-spontaneously-please-help/
> Apparently, the Windows 10 Installer does not properly manage permissions. If you do not want to lose customized permissions, the use Event Viewer, and it will state which folder is causing the issue.
>
> You do not need to purchase Windows Repair to be able to fix it. In the repairs, there is repair file permissions. I recommend it, as you do not have to do anything. If you modified many permissions, and want to keep them, then don't use Windows Repair, and instead do this:
>
> Open the properties of the folder, and go to security.
>
> Check who is the owner, if you are not the owner of the folder, then log into the owner of the folder (if you are not the owner, and you do not open the folder, explorer will not crash).
>
> Add yourself and give yourself full control (it is the bug where you are the owner, but you are not listed in the group)
>
> Reboot to make sure explorer is not crashing.
>
> If you are having difficulty trying to make the explorer window remain open, then turn on "Launch folder windows in a seperate process"
I'm wondering if maybe that's the issue, a problem with folder permissions. If so, how can I quickly find or correct the problem folders, I'm syncing thousands of them!
Though it's not very helpful, here is what eventvwr has to say:
The program FreeFileSync_x64.exe version 7.7.0.0 stopped interacting with Windows and was closed. To see if more information about the problem is available, check the problem history in the Security and Maintenance control panel.
Process ID: 9a8
Start Time: 01d1381d011befcc
Termination Time: 4294967295
Application Path: C:\Program Files\FreeFileSync\Bin\FreeFileSync_x64.exe
Report Id: 4bc8c7aa-a410-11e5-9bcd-ac72891de911
Faulting package full name:
Faulting package-relative application ID:
http://www.bleepingcomputer.com/forums/t/586464/windows-10-explorerexe-crashes-spontaneously-please-help/
> Apparently, the Windows 10 Installer does not properly manage permissions. If you do not want to lose customized permissions, the use Event Viewer, and it will state which folder is causing the issue.
>
> You do not need to purchase Windows Repair to be able to fix it. In the repairs, there is repair file permissions. I recommend it, as you do not have to do anything. If you modified many permissions, and want to keep them, then don't use Windows Repair, and instead do this:
>
> Open the properties of the folder, and go to security.
>
> Check who is the owner, if you are not the owner of the folder, then log into the owner of the folder (if you are not the owner, and you do not open the folder, explorer will not crash).
>
> Add yourself and give yourself full control (it is the bug where you are the owner, but you are not listed in the group)
>
> Reboot to make sure explorer is not crashing.
>
> If you are having difficulty trying to make the explorer window remain open, then turn on "Launch folder windows in a seperate process"
I'm wondering if maybe that's the issue, a problem with folder permissions. If so, how can I quickly find or correct the problem folders, I'm syncing thousands of them!
Though it's not very helpful, here is what eventvwr has to say:
The program FreeFileSync_x64.exe version 7.7.0.0 stopped interacting with Windows and was closed. To see if more information about the problem is available, check the problem history in the Security and Maintenance control panel.
Process ID: 9a8
Start Time: 01d1381d011befcc
Termination Time: 4294967295
Application Path: C:\Program Files\FreeFileSync\Bin\FreeFileSync_x64.exe
Report Id: 4bc8c7aa-a410-11e5-9bcd-ac72891de911
Faulting package full name:
Faulting package-relative application ID:
-
- Site Admin
- Posts: 7323
- Joined: 9 Dec 2007
Just to be clear, the crash-symptoms are not limited to FreeFileSync for "some folders" but also occur for Explorer? Is the problem reproducible?
The crash dump you sent (the 185 MB one) demonstrates the same problem like
https://social.msdn.microsoft.com/Forums/sqlserver/en-US/c33f9f63-a474-4188-8ce7-2ced131db469/why-does-ishellitemimagefactory-trigger-a-wmpaint-in-the-calling-application
or
http://comments.gmane.org/gmane.comp.version-control.subversion.tortoisesvn.devel/42671
and manifests as an endless recursion while rendering a generic "jpg" file.
However it's not clear if there is something that FFS could do about it.
It's possible/likely the problem is caused by some explorer extension.
Things start to go awry within a IImageList::Draw call which further down the call stack suddenly starts to pump Windows messages, effectively leading to an endless circle. All of this code is within Microsoft binaries so there is no peeking inside to find out what is going on in there...
The crash dump you sent (the 185 MB one) demonstrates the same problem like
https://social.msdn.microsoft.com/Forums/sqlserver/en-US/c33f9f63-a474-4188-8ce7-2ced131db469/why-does-ishellitemimagefactory-trigger-a-wmpaint-in-the-calling-application
or
http://comments.gmane.org/gmane.comp.version-control.subversion.tortoisesvn.devel/42671
and manifests as an endless recursion while rendering a generic "jpg" file.
However it's not clear if there is something that FFS could do about it.
It's possible/likely the problem is caused by some explorer extension.
Things start to go awry within a IImageList::Draw call which further down the call stack suddenly starts to pump Windows messages, effectively leading to an endless circle. All of this code is within Microsoft binaries so there is no peeking inside to find out what is going on in there...
-
- Site Admin
- Posts: 7323
- Joined: 9 Dec 2007
The smaller crash dump file (2 MB) is having problems for the same reason like the big one.
-
- Site Admin
- Posts: 7323
- Joined: 9 Dec 2007
The problem is definitively related to icon rendering:
On this site https://groups.google.com/forum/#!topic/tortoisesvn/oOzbLfSiDUw a user has found the following workaround:
toggling the default image viewer program
(and thereby the icon) onto / away from
Windows Photo Viewer immediately causes /
resolves the problem
On this site https://groups.google.com/forum/#!topic/tortoisesvn/oOzbLfSiDUw a user has found the following workaround:
toggling the default image viewer program
(and thereby the icon) onto / away from
Windows Photo Viewer immediately causes /
resolves the problem
- Posts: 5
- Joined: 9 Dec 2015
Many thanks! That seems to have fixed it!
