Hi!
This is not an issue with MS but I want to share this issue to see if anyone has also experience the same problem.
I have a script to automate a web site. The script was working fine till I installed the latest Windows 10 april update. The unquote string JSON ... message was display by MS. I start trouble shooting it to figure out that problem was not Google Chrome, not the Chromedriver but the Windows 10 update. By doing a rollback the script start working again.
I reported this issue at chromium.org. Will see how it goes.
April Windows 10 update & CHROMEDRIVER issue
Moderators: Dorian (MJT support), JRL
-
- Pro Scripter
- Posts: 90
- Joined: Fri Jan 31, 2020 10:52 am
-
- Pro Scripter
- Posts: 90
- Joined: Fri Jan 31, 2020 10:52 am
Re: April Windows 10 update & CHROMEDRIVER issue
Hello!
Just a followup .
Problem JSON.... came back. By updating from version 86 to 90 Google cause the problem.
I have to downgrade to version 86 et zip the Google update folder to hide the updater. Like that
the update can not been done. Problem fix for the moment till a fix is available.
Just a followup .
Problem JSON.... came back. By updating from version 86 to 90 Google cause the problem.
I have to downgrade to version 86 et zip the Google update folder to hide the updater. Like that
the update can not been done. Problem fix for the moment till a fix is available.
- Dorian (MJT support)
- Automation Wizard
- Posts: 1371
- Joined: Sun Nov 03, 2002 3:19 am
- Contact:
Re: April Windows 10 update & CHROMEDRIVER issue
I just updated my Chrome version to check. It's now version 90.0.4430.93. Downloaded and unzipped the latest Chromedriver from here, renamed my old chromedriver to chromedriver89.exe and replaced it with the new one. Rebooted just to ensure nothing was resident. Ran a test script which just starts and navigates - all worked as expected.
(Here's a link just in case you haven't seen this before).
(Here's a link just in case you haven't seen this before).
Yes, we have a Custom Scripting Service. Message me or go here
-
- Pro Scripter
- Posts: 90
- Joined: Fri Jan 31, 2020 10:52 am
Re: April Windows 10 update & CHROMEDRIVER issue
Thank you Dorian for response.
I managed to worked it out by blocking GoogleUpdate.exe with kaspersky firewall.
Like that it worked.
Looking at your reply I was not sure because I did all of what you wrote.
Any way! I give it a chance. Unblocked the exe, Google upgrade to version 90.
Download again the driver from your link. Rename the old one.
Start the Google example and failure. The JSON... error was back.
I managed to worked it out by blocking GoogleUpdate.exe with kaspersky firewall.
Like that it worked.
Looking at your reply I was not sure because I did all of what you wrote.
Any way! I give it a chance. Unblocked the exe, Google upgrade to version 90.
Download again the driver from your link. Rename the old one.
Start the Google example and failure. The JSON... error was back.
- Dorian (MJT support)
- Automation Wizard
- Posts: 1371
- Joined: Sun Nov 03, 2002 3:19 am
- Contact:
Re: April Windows 10 update & CHROMEDRIVER issue
Did you reboot? Are you 100% sure you're pointing to the new one?
Yes, we have a Custom Scripting Service. Message me or go here
-
- Pro Scripter
- Posts: 90
- Joined: Fri Jan 31, 2020 10:52 am
Re: April Windows 10 update & CHROMEDRIVER issue
Hi Dorian!
This morning I have done all steps again.
I made sure that Win 10 was up to date, Google and the driver same version.
Reboot, start the Google example script and it worked.
Thank you for your help in this matter.
This morning I have done all steps again.
I made sure that Win 10 was up to date, Google and the driver same version.
Reboot, start the Google example script and it worked.
Thank you for your help in this matter.
- Dorian (MJT support)
- Automation Wizard
- Posts: 1371
- Joined: Sun Nov 03, 2002 3:19 am
- Contact:
Re: April Windows 10 update & CHROMEDRIVER issue
Excellent!
Yes, we have a Custom Scripting Service. Message me or go here
-
- Newbie
- Posts: 1
- Joined: Thu May 20, 2021 10:59 am
Re: April Windows 10 update & CHROMEDRIVER issue
I have the same issue.