Opened 22 months ago

Last modified 21 months ago

#12744 new Bug report

Local file change monitoring only detects after file close on Windows 11

Reported by: Bas Owned by:
Priority: normal Component: FileZilla Client
Keywords: local file change monitoring windows 11 Cc:
Component version: 3.60.1 Operating system type: Windows
Operating system version: Windows 11 21H2 build 22000.778

Description

Hello,

On Windows 11 the local file change monitoring doesn't work. When I open the file and save it, the change popup in FileZilla doesn't appear. When I close the editing program and re-open it again, the popup apprears once the file editing software has re-opened.

I tested this with both Notepad++ and the built-in Windows Notepad.

I also tested this with Windows 10 and there I don't have the issue, I do however have this issue on all of my Windows 11 devices (3 different devices).

This issue is already there for at least a few months, I don't know exactly when it started but probably since Windows 11.

Regards,
Bas

Change History (4)

comment:1 by Tim Kosse, 22 months ago

Status: newmoreinfo

Sounds as if Windows 11 doesn't propagate file metadata changes.

If you save the file in your editor, does the modification time in Explorer immediately update?

in reply to:  1 comment:2 by Bas, 22 months ago

Status: moreinfonew

Replying to Tim Kosse:

Sounds as if Windows 11 doesn't propagate file metadata changes.

If you save the file in your editor, does the modification time in Explorer immediately update?

I thought the same, but yes, the modification time in Explorer changes immediately.

comment:3 by Tim Kosse, 21 months ago

Status: newmoreinfo

If you don't close the editor, are the changes being picked up if you switch to FileZilla and minimize and unminimize it?

in reply to:  3 comment:4 by Bas, 21 months ago

Status: moreinfonew

Replying to Tim Kosse:

If you don't close the editor, are the changes being picked up if you switch to FileZilla and minimize and unminimize it?

Yes, that seems to work.

Note: See TracTickets for help on using tickets.