Announcing Windows 10 Insider Preview Build 14352 Insider
-
After a reboot, Firefox behavior was worse if anything. The titlebar went blank after a minute, and weird large blank black window appeared against the blank white screen.
The good news is that an uninstall-reinstall seems to have totally cleared it up.
Good to hear that you found a way to fix that issue.
Jeff
-
-
Good to hear that you found a way to fix that issue.
Jeff
This was the first build (and I've tested them all since October 2014) that messed up FF. I wonder what happened? I'll probably never know!
-
This was the first build (and I've tested them all since October 2014) that messed up FF. I wonder what happened? I'll probably never know!
For me, this was the first build that had a minor issue with Office; when first booted to desktop after the upgrade, Skype for Business and OneDrive for Business which I have set to automatic start gave an error message about "We could not sign you in to Office". I had to end both processes from Task Manager, relaunch them and now they signed in without issues.
On a single upgrade I would take it as a harmless coinsidence, but this happened on two physical and one virtual machine.
-
This was the first build (and I've tested them all since October 2014) that messed up FF. I wonder what happened? I'll probably never know!
It sure is odd. I didn't have that issue with this build. And you're right.. we will never know what happened.
-
-
The store is broken for me in this build.
When I try to install something I get the "Working." and when I click to check updates there is no search feedback but after a few seconds it shows me the list of apps and in tells me that they were all updated a minute ago.
Tried wsreset but it didn't fix it.
-
You may wanna try uninstalling and installing back Firefox. You know. Like the Classic Shell issue. :)
Hahaha! Probably not a bad idea, Robot. First, though, I think I'll see if things are better this morning. Then a reinstall.
-
Nope,, it's working just fine for me so far. Has it cleared up yet??
Hmmmm, looks like it has, Jeff. I hadn't restarted since installation yesterday evening, but turned the 'puter off last night. Maybe that "restart" fixed the issue.
Note to self: Always restart the system engine after a new Build is installed. :)
-
Hmmmm, looks like it has, Jeff. I hadn't restarted since installation yesterday evening, but turned the 'puter off last night. Maybe that "restart" fixed the issue.
Note to self: Always restart the system engine after a new Build is installed. :)
You don't need a self note. The installation process will tell you to do so.
-
For me, this was the first build that had a minor issue with Office; when first booted to desktop after the upgrade, Skype for Business and OneDrive for Business which I have set to automatic start gave an error message about "We could not sign you in to Office". I had to end both processes from Task Manager, relaunch them and now they signed in without issues.
On a single upgrade I would take it as a harmless coinsidence, but this happened on two physical and one virtual machine.
I'm using Excel extensively, and so far haven't had any issues. Maybe I should have a test run with Skype for Business? :)
-
-
You don't need a self note. The installation process will tell you to do so.
Nah, as far as I'm concerned, that particular restart is a part of installation. I'm talking restart after I've actually signed in with my MS ID.