Chrome no longer opens file dialog

I was trying to upload a photo on Facebook and was unable to Friday night.  I figured it was a Facebook issue, but yesterday when I tried to download a file from here, the file dialog wouldn't open as well.  In fact it won't open under any circumstance now.  Most of the search links were old and even when I applied the fixes, no luck.  I thought it had something to with Flash, but even trying to save a webpage using file>save as... failos to produce a file dialog.

Possibly related, Shockwave Flash has crashed on this forum page.  I went to the chrome plugins list and tried to update but there aren't any.  There was a new Chrome but that didn't fix the problem.

Anyone have insight into this problem?

39,734 views 24 replies
Reply #1 Top

The hamburger icon on the upper right, click on it then scroll down to help then click on About Google Chrome. This will force an update. Maybe this will help.

Reply #2 Top

Same thing has been happening to me, I have to reboot every time it happens to solve the problem, but then it comes back. For instance, when uploading to WC, when I click the button to upload the screenshot or file, nothing happens. When right clicking on an image and then click "Save Image As", nothing happens, no dialog window, and again I have to again reboot.  :S

 

The problem does not occur in IE, just Chrome, and the latest version is what I have installed.

Reply #3 Top

I was having a little trouble with Chrome being a little spastic a few days ago and I went in and disabled hardware acceleration again (I had disabled it on the previous version of WB, then gone back in and enabled it after the WB update).  That seems to have taken care of it for me (and honestly I can't see any difference between hardware acceleration enabled/disabled otherwise).  Might be worth a shot.

Reply #4 Top

IE works real good......    :-"

Reply #5 Top

Chrome has been acting up of late. The throbber sometimes freezes, starts up again as the page is loading then freezes again. It doesn't happen here but when I go to yahoo sometimes the page will go black and mousing over clears part of it but I have to refresh the page to clear it all. I don't know if its a site issue or Chrome's new version is at fault. Same thing happened before I updated it.  

Reply #6 Top

gevansmd - 

It might be related (or not), but have you updated your Windowblinds to the latest version?

I had similar issues, and after updating, things were magically fixed.

Reply #7 Top

Quoting DrJBHL, reply 6

gevansmd - 

It might be related (or not), but have you updated your Windowblinds to the latest version?

I had similar issues, and after updating, things were magically fixed.

 

I did but then restored the prior version.  The new WB beta breaks the built-in Windows 10 State Menu when you look at all programs.  Large letters of the alphabet are placed in two columns over the program names.  Support was unable to fix the problem but reinstalling the prior WB did.

Reply #8 Top

Quoting Uvah, reply 5

sometimes the page will go black and mousing over clears part of it but I have to refresh the page to clear it all.

That's one of the things it was doing to me before I unchecked "Use hardware acceleration when available" this last time around within Chrome's advanced settings.

Reply #9 Top

I reinstalled the latest WB beta and the Start Menu problem has gone away.  However, still having the Chrome file dialog issue.  Unfortunately, rebooting doesn't fix that for me.

Reply #10 Top

There's something more going on...have you disabled or enabled hardware acceleration...undo whatever it is now (make sure it's disabled).

Tell us a bit more about your computer...maybe a screeny from Speccy?

Reply #11 Top

I had previously tried disabling hardware acceleration.  I even reset to default settings that unloads the extensions.  None of that worked.

However, I discovered now, if I unload WindowBlinds, the problem goes away.  

Reply #12 Top

I reloaded WB and changed blinds and the problem has gone away.  The issue seems to be with the Reddish blind. Changing blinds also got rid of the shockwave crash.  very strange but applying the Reddish blind is the only recent change I made to my PC.   

Reply #13 Top

Quoting gevansmd, reply 12

I reloaded WB and changed blinds and the problem has gone away.  The issue seems to be with the Reddish blind. Changing blinds also got rid of the shockwave crash.  very strange but applying the Reddish blind is the only recent change I made to my PC.   

 

I tested the skin gevansmd, and apparently my Reddish skin, and the base skin I used to create it called Scarlet, both cause this issue. I have absolutely no idea why though and the only problem with those two skins is in Chrome. I will try and resolve this issue, but I have absolutely no idea where to even start. None of my other skins have the issue, just those two. I apologize for anyone having this issue and I hope to resolve it quickly.  :(

 

Maybe someone in support could have a look at either of those skins and see if they notice anything? It would be greatly appreciated.  :)

Reply #14 Top

Tom, and gevansmd:

I've moved the post to Stardock Support...I think it probably would have been better posted there, but definitely since Lightstar has posed the secondary question.

Also Tom I suggest you send a query to Support, separately.

Reply #15 Top

Well, I looked through everything and cannot see what is causing this issue, so I have asked for assistance from support. Ticket# KRC-836-86635.

Reply #16 Top

Just installed Reddish and thought maybe the problem wouldn't occur as sometimes happens but no luck. Dialogue box does not open.

Reply #17 Top

The issue with Reddish has been found and the next WB update should address this.

Reply #18 Top

What was the problem?

Reply #19 Top

Quoting Uvah, reply 18

What was the problem?

 

I am waiting for a reply from support so I can fix Reddish and Scarlet Ross, as soon as I find out I will modify and upload the fixed WB's.

 

EDIT: Doesn't make sense to me, but evidently the problem may be with WB and not Reddish or Scarlet. It doesn't make sense because only those two skins have the issue, so how can it be WB itself? Also, the problem occurs it in WB 8.13 and WB10. Crazy....  :S

Reply #20 Top

I'm only guessing here but could it have something to do with the UIS text or whatever you call it?

Reply #21 Top

I went through the .UIS file thoroughly Ross, I did not notice anything that might be causing the issue. Still waiting for information from Neil or support.

Reply #22 Top

Ok. It was just a thought.

Reply #23 Top

I would really like a reply to my PM to Neil or my last response to support on this 2 days ago.

I am assuming now that the issue was within WB10 itself and not the skin, but I am confused. How can it be just 2 skins that are causing the issue in Chrome, when all my skins are designed the same way?

 

Thank you.

 

EDIT: Heard back from support, the problem is not with my Reddiish skin:

 

WB will be modified to adapt to a Chrome issue. It will be in the next mini update.


Good to hear on my end!  :)

Reply #24 Top

Well I'll be buggered! I had Reddish installed but didn't put it through its paces. Hindsight being what it is I should have.  :blush: