Windows 10 Build 10130 Hands On Review
Here is our Windows 10 Build 10130 Hands On Review.
I have been using Build 10130 for a week now, and have had a rather mixed experience with it.
It is definitely an improvement over Build 10122. The performance of Build 10130 is comparatively better. In the prior build, Microsoft Edge, aka Project Spartan would crash often, despite this machine being an Intel laptop. But, Spartan in Build 10130 works just fine.
We have already reported about the Known issues in Windows 10 Build 10130. But, there are a few unreported issues too. Here are the bugs in Windows 10 Build 10130 that I ran into:
Start Menu and the Taskbar do not respond:
This has been the most problematic area in Build 10130. The Status Bar and the Start Menu would freeze occasionally for me. The only workaround is to restart the system. But this appears to have been a temporary issue, which could have been fixed by Windows Updates. (more about this below)
Sometimes a Critical error message would pop-up with the following message:
A Critical error has occurred in the Shell Infrastructure Host. Start Menu, Cortana, and some apps may not be available. Please save your work and sign-out to recover.
The window had an option to Sign out now, but even after clicking on the sign out button, and signing in, the issue wasn’t solved. Although I could drag the Window to the edge of the screen, and continue working in apps already opened, I couldn’t open any new apps. So I had to reboot the system to resume my work.
Fortunately I haven’t run into this issue for a few days now. Microsoft may have fixed it in an update, but the only ones I can see in Windows Update History (and uninstall updates) are KB3069065, which fixes crashes in Outlook Mail, and KB3069068, which fixes WiFi connectivity issues.
Note: The Windows Update KB3069068 has a bug in it, as the Windows Update history lists that “KB3069068 Requires a restart to finish installing” Choosing to uninstall updates, however, shows that the update is already installed.
Windows Explorer Crashes during Shut Down:
Shutting down Windows 10 Build 10130 would throw out an error related to explorer.exe, with the following message:
The instruction at 0x00007FF849E2CC60 referenced memory at 0x0000000000000000. The memory could not be read. Click on OK to terminate the program.
(I snapped this photo today)
Just clicking on the OK button allows the system to shut down. This appears to be a known issue as reported on Twitter.
USB devices cannot be safely removed:
Windows 10 seems to have a bug related to USB devices (External Hard Drives, Flash Drives), etc, which prevents the operating system from stopping the devices. This prevents the user from safely removing the device. The only workaround is to shut down the computer and unplug the device.
Technically this isn’t a bug, but a minor annoyance. Ever since I upgraded from Windows 8.1 to Windows 10, my laptop has been booting very slowly. I have just the basic apps enabled for start-up, and it still takes well over a minute to boot up. Maybe even more.
Fast Start Up and Hibernating, aren’t really helpful with the crashes and hang ups.
I have been considering to downgrade to Windows 8.1, and use Windows 10 in a virtual machine, like I did earlier. But I am just not sure about it, especially since we know Windows 10 is releasing on July 29th, which is just less than two months away.