FC 876 Error message when exiting 64-bit FC

Bugs and issues - current donor version.
Message
Author
yom417
Posts: 21
Joined: 12.06.2016, 02:53

FC 876 Error message when exiting 64-bit FC

#1 Post by yom417 » 11.11.2022, 09:23

I have been getting this error since upgrading to FC 876.
It seems to happen when I have other applications running at the same time.
Downgrading to 875 or 874 does not cure it.
This does not happen with the portable version.
Image

yom417
Posts: 21
Joined: 12.06.2016, 02:53

Re: FC 876 Error message when exiting 64-bit FC

#2 Post by yom417 » 11.11.2022, 09:29

sorry image is here.
https://postimg.cc/JsJtM75V

Marek
Author
Author
Posts: 3973
Joined: 10.04.2006, 09:48
Location: Germany
Contact:

Re: FC 876 Error message when exiting 64-bit FC

#3 Post by Marek » 11.11.2022, 15:41

Use "send bug report" or "save bug report" and send me the report.

yom417
Posts: 21
Joined: 12.06.2016, 02:53

Re: FC 876 Error message when exiting 64-bit FC

#4 Post by yom417 » 12.11.2022, 02:56

Thunks Marek.
I send bug report to you.

yom417
Posts: 21
Joined: 12.06.2016, 02:53

Re: FC 876 Error message when exiting 64-bit FC

#5 Post by yom417 » 20.11.2022, 02:30

I updated to 877 and still get the same message.

Marek
Author
Author
Posts: 3973
Joined: 10.04.2006, 09:48
Location: Germany
Contact:

Re: FC 876 Error message when exiting 64-bit FC

#6 Post by Marek » 20.11.2022, 21:03

You have written:
This occurred when starting FC at the same time as EDGE and exiting both.
Unfortunatelly, I can not reproduce such error.

yom417
Posts: 21
Joined: 12.06.2016, 02:53

Re: FC 876 Error message when exiting 64-bit FC

#7 Post by yom417 » 26.11.2022, 02:36

This seems to happen after updating to Windows 11 Pro 22H2.
I will do a clean install of Windows 11 in the near future.

horst.epp
Posts: 460
Joined: 15.11.2008, 20:18

Re: FC 876 Error message when exiting 64-bit FC

#8 Post by horst.epp » 26.11.2022, 12:08

yom417 wrote: 26.11.2022, 02:36 This seems to happen after updating to Windows 11 Pro 22H2.
I will do a clean install of Windows 11 in the near future.
There are no such problems here after upgrading to Windows 11 and any of its official updates.
Windows 11 Home x64 Version 23H2 (OS Build 22631.3296)
Everything Version 1.5.0.1371a (x64), Everything Toolbar 1.3.2, Listary Pro 6.3.0.67
FreeCommander XE 2024 Build 905 64-bit donor

yom417
Posts: 21
Joined: 12.06.2016, 02:53

Re: FC 876 Error message when exiting 64-bit FC

#9 Post by yom417 » 25.12.2022, 02:22

I did a clean install of Windows 11 PRO (22H2) but it does not cure the error message after FC is closed.
Maybe there is a conflict with some app, but I don't know.
I have tried uninstalling all the apps I can think of, but the situation remains the same.
I have no problem with this error message because it doesn't change anything in FC, but it's a hassle to clear the error message every time.
I would appreciate it if you could prevent the error message from appearing in the settings.

User avatar
Dreamer
Site Admin
Posts: 6113
Joined: 19.08.2007, 23:40

Re: FC 876 Error message when exiting 64-bit FC

#10 Post by Dreamer » 25.12.2022, 15:14

yom417 wrote: 11.11.2022, 09:23This does not happen with the portable version.
What is the installation path for install and portable version? These versions should be the same, so the path could be the only difference.

You can try to install FC to the other path, or just change the path for the settings folder in Setting - Start program - Configuration folder, to FC install folder (if it's not the Program Files), or to "Following folder", just don't use any system path, not C:\ or C:\Program Files .

For install path or/and custom settings path you can use e.g.: C:\Programs\FreeCommander and C:\Programs\FreeCommander\Settings .

yom417
Posts: 21
Joined: 12.06.2016, 02:53

Re: FC 876 Error message when exiting 64-bit FC

#11 Post by yom417 » 26.12.2022, 04:00

I forgot to mention that I got the same error after using the portable version a few times.
The installation path is C:\Program Files\FreeCommander XE.
This is the default installation path for FC.
The portable version is "C:\PortableProgram\FreeCommanderXE-64-donor_portable880".

yom417
Posts: 21
Joined: 12.06.2016, 02:53

Re: FC 876 Error message when exiting 64-bit FC

#12 Post by yom417 » 26.12.2022, 04:24

The windows administrative event shows the following error.

"Event 1002 Application Hang
The program FreeCommander.exe version 2022.0.0.880 has stopped interacting with Windows and has been closed.
To see if more information about the problem is available, please check the problem history in the Security and Maintenance control panel."


Is there a problem with the my network?

yom417
Posts: 21
Joined: 12.06.2016, 02:53

Re: FC 876 Error message when exiting 64-bit FC

#13 Post by yom417 » 20.03.2023, 08:54

This phenomenon is quite common in Japan on Windows 11 PRO 22H2.
There are several cases up on the Japanese FC bulletin board.

It has already been 4 months since it occurred, but I still get the error message when exiting.
I have tried to do things like terminate most of the network and resident apps, but to no avail.

If this error does not occur on Marek, it may be a phenomenon unique to Japanese Windows 11,
but it is also troublesome to exit the message again when exiting, so I would like some countermeasure.

yom417
Posts: 21
Joined: 12.06.2016, 02:53

Re: FC 876 Error message when exiting 64-bit FC

#14 Post by yom417 » 26.03.2023, 03:34

Error message no longer appears.

1. Update to Windows 11 PRO 22H2 KB5023706
2. Push the Ignore Local Security Agency Protection button in Windows Security
3. Update AMD motherboard chipset to the latest
4. Update the BIOS of AMD motherboard to the latest version.
5. Update the LAN driver of INTEL to the latest version.

I guess any of the above 5 points worked and the error message no longer appears. (There is a big possibility of 2 or 3.)

yom417
Posts: 21
Joined: 12.06.2016, 02:53

Re: FC 876 Error message when exiting 64-bit FC

#15 Post by yom417 » 02.08.2023, 12:28

I thought this error had stopped appearing, but the error started appearing soon afterwards.
This error seems to occur in the Japanese Windows 11.

Post Reply

Who is online

Users browsing this forum: No registered users and 27 guests