Just recently upgraded my laptop to run on Windows 10 (from Windows 8.1). Even though I haven’t been “notified” by Microsoft that it was my turn, I confirmed that the hidden folder was indeed on my computer.
On a side note, I went ahead and followed the directions from Microsoft to download and create a bootable upgrade USB stick and when I did, the original upgrade directory changed from c:\$Windows.~BT to c:\$Windows.~WS\Sources. This was in case, down the road, I wanted to do a clean install rather than an upgrade.
For now though, here are the first issues I’ve run into during the transition
- Google Chrome – I was unable to get Google Chrome browser to work at all until I had installed the Dev version. Canary build also works but that is a little too out there on the edge for my liking. Neither Stable or Beta would go anywhere; you could launch the app but that was it. Anywhere you attempted to load (even chrome://extensions) will result in the Kill/Wait screen.
- Despite running x64 Windows, your best bet with Chrome is to stick with the 32-bit version of Chrome. I tried all versions of the 64-bit version of Chrome and, as above, only the versions that worked were Dev and Canary versions. The problem is that plugins (Flash and some others specific media) won’t play properly in the 64-bit version. So if you want to take advantage of Chromecast app, you are going to want to stick with a 32-bit version of Chrome.
- Ran into problems with IIS (used locally for development purposes) where the App Pool kept crashing which would lead to a 503 error when going to localhost. The solution to the problem was to turn off “Enable 32 bit applications to run” per this TechNet article.
After running Windows 10 for a few days, that is all I’ve found that prevented me from working. How about you? Have you hit any walls yet running Windows 10 on your day to day computer?
- Setting up SSL on Amazon Linux Instance under EC2 - July 26, 2018
- Method Chaining of Objects in C# - January 16, 2017
- Native SQL Backup And Restores on AWS RDS - November 9, 2016