After Win7/Win8.1 upgrades Win10, the built-in application requires additional installation time. Users are patiently waiting for

Win10 is being pushed to Win7/Win8.1 to upgrade users. At present, some users have completed installation in this way. However, this does not mean that the Windows 10 installation is successfully completed. Many users report that after the installation is finished, they will enter the Win10 desktop. Windows applications (original Modern/Metro applications) such as the start menu, built-in applications, and settings cannot be opened normally, and serious carding may occur. Flashback and other phenomena.

The possible reason for this phenomenon is that although Win10 ended the installation process, it did not complete the installation of the built-in application. This sounds incredible, but it is really the case. Some users report that when the start menu is opened for the first time after the installation, “Settings” has not been installed yet. A long list of application codes appears, not to mention other Windows applications. Basically, there is no available.

But after a period of built-in Windows application installation, you need to manually restart the system two or three times (this is not Microsoft requirements, but experience). You will then find that these apps may get up and running as long as your network is good enough to not affect the built-in app download and installation process.

This method generally requires the user to wait patiently for the Win10 application to complete the subsequent installation. Perhaps Microsoft is afraid that users will be in a hurry in the final stage of the installation process, so they will let users enter the desktop in advance in the case of "almost". But the result of this approach is also obvious, and many users will think that Win10 can't use it normally. This will not only affect the normal use of the user, but also affect the reputation of Win10, so Microsoft should also make more efforts in the optimization of the installation program to avoid such an event. If this doesn't solve the problem, you'll need to wait for an official Microsoft patch or other further solution.