RECOMMENDED: Click here to fix Windows errors and optimize system performance
Windows 8 was made available to the public after hard work and testing this year’s beta editions. At the time of the beta tests, the errors were obvious and bloggers like me cited them in our messages. At the time, we did not take them seriously and we jumped them because we are sure they will be withdrawn.
But it seems that there are still bugs in the final version of Windows 8. Today, in this article, I will tell you how to find a simple bug in the Desktop panel.
1 Go to Desktop and right click and select New -> Shortcut.
2 In the Create shortcut window, cancel it by clicking Cancel. This deletes the default icon created in the background.
3. 12) Everything will be fine until then. But now right click again and you will find Undo New – Ctrl+Z.
4 Click this option and you will be directed to the Items Not Found window, as shown below:
5 The error does not stop here, if you press Skip in the window shown above, then you explore a new menu in the context of Redo New – Ctrl+Y.
So far this error is similar to Windows Vista and I was wondering how Microsoft didn’t notice this. I have the feeling that such an error does not occur under Windows 7 as we tested it. Let’s take the technical part.
If you cancel the link creation, the link will be deleted as you wish. For this reason, you receive an error message indicating that the file to be deleted has not been found. Undo thinks that a creation process has occurred and he tries to undo it, but the undo deleted the file before he had the opportunity to undo it
When it is re-run, the empty shortcut is created and the empty shortcuts cannot be set. This is just one of the things that happens in complex systems, some operations conflict with others(16)(2)
In fact, it is because the Explorer thinks a shortcut has been created that displays the option Undo New. In fact, the explorer (16) believes that a shortcut was created because a shortcut was created. However, clicking Cancel deletes it.
We hope that Microsoft will correct this error as soon as possible via Windows updates.