Page 1 of 1

I have this error on new version 23.50.0.200

Posted: 26 Aug 2022 18:37
by Fushko
Error: 13 (0x0000000D)
Desc: Type mismatch
Dll: 0
Proc: CacheData@0 - Count: 1, Write: False, Path: C:\Users\Jose Luis De Moura\AppData\Roaming\XYplorer\Thumbnails\ac68e5f3b4e91e0221a3ae8e157ae526.ini

Source: XYplorer
XY ver: XYplorer 23.50.0200
OS: Windows 10 Windows 10, 64-bit, Release 2009, Build 19044.1889
Locale: 1033 (en-US)
ANSI: 1252, ACP: 1252 (ANSI - Latin I)
Font: Segoe UI 10,5, Segoe UI 9, DBCS: No
DPI: 96 (100%), 1920x1080

Date: 2022-08-26 12:27:25

Image

Re: I have this error on new version 23.50.0.200

Posted: 26 Aug 2022 18:48
by admin
Hm. Can you send me that ac68e5f3b4e91e0221a3ae8e157ae526.ini file per email?

Re: I have this error on new version 23.50.0.200

Posted: 26 Aug 2022 20:32
by Fushko
I can´t send you ini file because i clear cache thumbnails.....
this error is always when i navigate up or down, or any location with this version,

I downgraded to version 23.50 and the error is gone.....

when i upgrade to 23.50.0200 the error still again....

Re: I have this error on new version 23.50.0.200

Posted: 26 Aug 2022 21:14
by admin
The next beta might show a better error message...

Re: I have this error on new version 23.50.0.200

Posted: 01 Sep 2022 16:51
by 2C523AEC9B
Hi there, i've also got this error.

Code: Select all

Error:  	13 (0x0000000D)
Desc:   	Type mismatch
Dll:    	0
Proc:   	CacheDataIni@72

Source: 	XYplorer
XY ver: 	XYplorer 23.50.0300 (Virgin)
OS:     	Windows 10 Pro, 64-bit, Version 21H2, Build 19044.1889 (10.0)
Locale: 	2058 (es-MX)
ANSI:   	1252, ACP: 1252  (ANSI - Latín I)
Font:   	Segoe UI 9, Segoe UI 9, DBCS: No
DPI:    	144 (150%), 2160x1440

Date:   	2022-09-01 09:11:24

Re: I have this error on new version 23.50.0.200

Posted: 01 Sep 2022 17:43
by admin
Thanks, that error message helped me fixing it. :tup:

Re: I have this error on new version 23.50.0.200

Posted: 02 Sep 2022 08:12
by admin
Is it fixed now?

Re: I have this error on new version 23.50.0.200

Posted: 05 Sep 2022 07:14
by Fushko
The error continue on version 23.50.0.200 and 23.50.0.300

But on version 23.60 its gone.

Thx for fixed.