system error code 1400 invalid window descriptor

Report a bug or a problem.
Post Reply
hopalongrock
Sr. Member
Sr. Member
Posts: 289
Joined: Wed Sep 15, 2010 1:38 pm

system error code 1400 invalid window descriptor

Post by hopalongrock »

(translated from Hungarian).
Very rarely do I get this error, and only now realized the reason:
somehow the explorer stopped and restarted (Either by me or a program).

After pressing OK, It seems that TGF is working further, but I rather stop and restart it, without any problem.
Using XP SP3.

(I do not have this problem with other programs)
Attachments
system error.jpg
system error.jpg (9.52 KiB) Viewed 7372 times

User avatar
jtclipper
Administrator
Administrator
Posts: 768
Joined: Tue Aug 10, 2010 12:04 pm

Re: system error code 1400 invalid window descriptor

Post by jtclipper »

You mean windows explorer?

hopalongrock
Sr. Member
Sr. Member
Posts: 289
Joined: Wed Sep 15, 2010 1:38 pm

Re: system error code 1400 invalid window descriptor

Post by hopalongrock »

Yes.

For example, yesterday I tried a junkware removal program, probably it stopped and restarted the windows explorer, but I don't know/remember exactly.

User avatar
jtclipper
Administrator
Administrator
Posts: 768
Joined: Tue Aug 10, 2010 12:04 pm

Re: system error code 1400 invalid window descriptor

Post by jtclipper »

This probably happens only on XP since I can't reproduce and It might prove cumbersome to find and fix if it is even possible

hopalongrock
Sr. Member
Sr. Member
Posts: 289
Joined: Wed Sep 15, 2010 1:38 pm

Re: system error code 1400 invalid window descriptor

Post by hopalongrock »

jtclipper wrote:This probably happens only on XP since I can't reproduce and It might prove cumbersome to find and fix if it is even possible
Thanks, it's a rare and caused no harm.
(Otherwise it's "Invalid window handle" as I found with Google.)

waleeedijaz
Newbie
Newbie
Posts: 1
Joined: Fri Mar 04, 2016 1:11 pm

Re: system error code 1400 invalid window descriptor

Post by waleeedijaz »

The error message occurred after both an installation of version .80 over a long used (and wonderful) installation of version .72 and it occurs after an uninstallation of the previous version and a clean installation.

Post Reply