Microsoft Corporation on the latest version of the operating system Win10 shows us the wonders of the possibilities of updating. Everyone who does not want to lose data from the
1903 update is welcome to cat.
A few points that are rarely paid attention to in support of Microsoft are the assumptions of the author of the article, published as a result of experiments, do not claim to be reliable.
- There is a list of applications that will clearly survive any update. Some legacy applications may break the update due to undocumented features.
- Windows 10 is actively promoting the concept that the best software tester is the user.
- If you accidentally work with a large collection of multimedia and mobile devices from Microsoft, the system may collapse due to undocumented indexing algorithms
Rarely mentioned Wikipedia information regarding UWP
Read only to hardcore developers Universal Windows Platform (Universal Windows Platform, abbreviated as UWP) is a platform created by Microsoft and first introduced in Windows 10. The purpose of this platform is to help create universal applications that run on both Windows 10 and Windows 10 Mobile without changing in code. There is support for creating such applications in C ++, C #, VB.NET and XAML. The API is implemented in C ++ and is supported in C ++, VB.NET, C #, F # and JavaScript. Designed as an extension for Windows Runtime (the platform introduced in Windows Server 2012 and Windows 8), it allows you to run applications on different hardware platforms.
So, the theoretical information is built. Let's move on to practice.
I bought a fresh laptop under 10-ku.
I was surprised that after connecting the second hard drive, the media files were indexed for a very long time. To work with multimedia on external devices, a long time ago I installed a Zune player. The system began to be updated out of place. As a result, with the 1903 update, I was kindly allowed to choose the time for the update.
I chose ...
Typically, Windows 10 updates when it sees updates. But! The 1903 update was large-scale and after three hours of operation, the computer began to show utter things.
I started to install the update - I lost the user.
% Username% .0001 ...
There was a username, and after a reboot it changed. It turned out that this is a reaction to the media player.
There were two discs. One system, another for data.
The second disk turned out to be a brick.
This means that for unknown reasons, from the beginning and end of the disk from the Windows snap-in, it was cut off by megabytes under an unknown file system.
I look at what happened.
It became necessary to run the snap-in to remove these changes.
But the worst thing is that because of the media player, the update could not record in
user system settings. Probably no one thought about it.
As a result, the update copied the user's files to the new user, and now the computer will not be able to enter the network due to the fact that there is no user in the domain, the registry has flown, because many programs, resources and icons are sharpened under the username.
You will have to rename the user in the registry manually, reinstall
part of the programs and clean up the thousands of files referenced
resources.
Here is the player for you - he was able to ditch the update!
So much for the update - it ruined the system.
But the registry is still broken!
And Microsoft does not have a good editor (or, better, an application rollback mechanism).
And the start button - the UWP application - disappeared forever after trying to return the username to the registry.
A few words in conclusion of the article.
- If it were not for the structure of drive C, then most likely there would have been a brick. If there was only one disk, the probability of data loss would increase many times over.
- The update destroyed the domain record, the program will have to be reconfigured, even Visual Studio from Microsoft has not suffered such an attack.
- It was experimentally established that UWP applications still store user information somewhere, but there is no effective means of working with user information UWP, moreover, there is a suspicion that due to the fact that developers for Android and iOS are in no hurry to port their applications for Windows Mobile, the standard will not be supported and developed in the future.
People what to do with such an update?