Division

Genre

Software/Hardware

Process

Posting locale

Questions

No questions/answers found

Please try the following:

Try using fewer keywords or search terms
Try a different keyword or search terms

If you couldn’t find the information you are looking for, ask a question to solve your problem.

Ask a Question Now!

Resolved

Script Error After 1.6.8 Update

VIEW 1,478
Total 2

- Report to administrator

Shizby

I've been getting this script error ever since I upgraded to the newest version. I don't have Internet Explorer installed on my PC (Windows 10 Pro). I've gone into Control Panel > Internet Options and cleared the cache there. Didn't work. I've used the Disk Cleanup utility to clear the cache that way, but I'm still getting this error. I've gone and manually deleted everything from %AppData%/Microsoft/Windows/INetCache but the error remains.

Has anyone solved this? Or is it just a bug in the latest release?

Published date : 6 years ago

Updated date : 6 years ago

English

Best Answer

hakokoto ◆

6 years ago
- Report to administrator
It seems fixed for me after updated to Windows10 Fall Creators Update, but I am not sure if this is the cause.
Anyway it seems fine now for me.
...View more
Message
- Report to administrator
Shizby

6 years ago

It's gone for me as well after the Fall Creator Update.
- English

hakokoto ◆

6 years ago
- Report to administrator
I have the same issue, clean IE cache did not fix the issue.

It seems not caused by update, I tried roll back to 1.6.7 and CLIP Studio shows the same error message at start page. I remembered 2 days ago when my CSP updated to 1.6.8 this issue did not exist, but seems from yesterday it starts to happen.

By the way I am using Traditional Chinese version, Windows10 Pro. Korea version seems has the same issue.
https://ask.clip-studio.com/zh-tw/detail?id=3270

So I wonder this is some server side issue, not user side.

The error script seems all the same , it is "https://connect.facebook.net/signals/config/892475647458881?v=2.7.23".
- English
Dalibor

6 years ago
- Report to administrator
Same error here too. Right after this new 1.6.8 update. I'm using Win7 Pro.
- English
Rafchu ◆

6 years ago
- Report to administrator
Same error too, on Win7 pro also.

I used to have this error a lot before the 1.6.7 upgrade, which fixed it.
Now the error is back with the 1.6.8 upgrade ^^;
- English
hakokoto ◆

6 years ago
- Report to administrator
It seems fixed for me after updated to Windows10 Fall Creators Update, but I am not sure if this is the cause.
Anyway it seems fine now for me.
- English
...View more