Windows 10 build 16193 bugs: Installation fails, non-running apps, and more

Madalina Dinita
by Madalina Dinita
Affiliate Disclosure

The upcoming version of Windows 10 scheduled for release in September now an official name: Windows 10 Fall Creators Update. And with this announcement. Microsoft recently rolled out build 16193, revealing the first major big change coming to the Windows 10 Creators Update this fall.

At the same time, Windows 10 build 16193 also brings issues of its own. In this article, we’re going to list the most frequently encountered build 16193 issues that Insiders reported on Microsoft’s Support forum.

Windows 10 Fall Creators Update build 16193 bugs

Download and install issues

Apparently, installing build 16193 is not an easy task for all Insiders. Many are still struggling to complete the installation process, due to various issues:

  • Errors 0x80070002, 0x80070003, 0x080070005 are blocking the process
  • PC rolls back to the previous build version
  • No error message appears, but the install process gets stuck
  • The build doesn’t get passed the first restart.

Windows 10 Insider Preview 16193.1001 (rs_prerelease) – Error 0x80070002

I’m getting this error when I try to install with windows update. Uninstalled Malwarebytes. reboot laptop. Still get the error. […] It downloads ok but when updating at 5% it jumps to 100% and then displays the error.

Apps won’t run

Insiders report that they can’t open many of the apps installed on their computers after installing build 16193.

After installing Insider release 16193 ( from 16188) I could not run any installed apps.  Also when I ran File Explorer it took over a minute for the green search bar to complete.  I was able to roll back to 16188, only by using the option in “stop insider builds”.  After rollback, the computer is running normally.

My People breaks Windows 10

Insiders report that My People causes a series of issues when placed on the taskbar, including the File Explorer not opening, Internet Explorer being unresponsive, Windows crashing, and more. Turning My People off seems to fix all these issues.

After getting past the login screen, the Taskbar would flash and reset every 15 seconds or so.  I found that clicking the My People icon caused the Taskbar to flash and reset immediately.  Aha!  That must be the culprit!  I was able to get into Taskbar settings and turn My People off.  Then things started to calm down.  Windows seemed to function properly on the limited Safe Mode basis.  I was able to use File Explorer ok, and access the Web using Internet Explorer.  Leaving the My People Taskbar setting to Off, I restarted.

Finally Windows booted normally without crashing.  I just updated the Store apps successfully.

These three issues are the most common problems caused by build 16193. If you’ve encountered other bugs, tell us more about your experience in the comment section below.


This article covers:Topics:

Leave a comment below!

add a comment

Leave a Reply

Your email address will not be published. Required fields are marked *

It seems my 64 bit programs run as normal while the 32 bit have issues. I turned off developer mode and selected side bar and half of my apps/programs are not working but still no 32 bit programs.

A Dll in one of may apps (fastHelp) is reporting A Bad Image error 0xc000007b, and i just cant seem to cure it after 2 days of trying, it’s really starting to pee me off and rolling back will cause me a lot of work grrr

My problem is very little will run after the latest update, that includes ReimagePlus so I can not fix anything, nothing will uninstall either. Seems this build has stopped everything except microsoft software from ruhning.

Build 16193, Lenovo Y570 laptop, problem with integrated video card HD Graphics 3000: “Windows has stopped this device because it has reported problems.” Second display doesn’t work. I had to roll back to previous build.

After updating to build 16193 I had problems starting Hauppauge WinTV V8.0 and Corel Quattro Pro. I didn’t spend much time seeing what other problems there were but ended up going back to build 16188.