The Italian version of the bug exposes Vista "congenital" less than

Joseph Fieber is the founder of itsvista, who has more than 20 years of experience in the IT industry. Recently on the itvista website, he described this to us: One of my readers described a bug in Vista that has not been archived. This reader is using Windows Vista in Italian. According to him, when he copies files on the command line, the system gives the option "Yes| No| All”, but when executed, the corresponding option does not match the actual action. When you select "No", the system does perform the copy action! I looked at the Microsoft Knowledge Base and found an article that was consistent with what the reader described, but this article is not for Vista, but for Windows Server 2003. Why a Windows 2003 bug will appear in the Vista system, Paul Thurrott (edited by windowsitpro.com, IT industry veteran) explained: The new version of Windows is usually built on the existing Windows system, Microsoft When the Longhorn development team was rebuilt to develop the Windows Vista system we have seen so far, the original prototype was Windows Server 2003 SP1. But when the development work began in 2001, it became Windows XP-based. By the middle of 2004, the development team found that building the Windows Vista system described in the Roadmap based on the code of Windows XP has been difficult to make, and the development is deadlocked. So when Microsoft started the development of Windows Vista again, it had to return to the original idea of ​​Windows 2003 SP1 instead of Windows XP. Let's go back to the problem mentioned by my readers. As you can see from the picture below, he uses the Vista system, and the figure clearly shows that the choice is "n-NO" (that is, no Copy the file), and Vista executes the copy operation (3 file copiati):

Based on the description of the Microsoft Knowledge Base, we know that this is due to Windows Server 2003. The Ws03res.dll resource file is not properly implemented by the localization of Italian. At this point, a more important issue appeared in my mind. Microsoft knew that this was a problem with Windows Server 2003, but they also knew that Vista (and the unreleased Windows Server 2008) was developed on the basis of Windows Server 2003. But there isn't any solution for this problem under Vista, and there are no other Vista-related articles that describe the problem to the reader, although Microsoft employees have spent time and provided patches for this issue (but only For Windows Server 2003 SP1). Does Microsoft divide Vista and other systems too clearly? When a group of developers used another set of code, did they not discuss this issue? Is this one of the benefits of shared code? Although this is only a small problem, it will lead to public curiosity. How many similar problems exist in Windows Server 2003, which have been discovered, but there is no solution for Vista? Therefore, if you find a problem in the Vista system and can't find the answer in the Vista knowledge base, you can go to the Windows Server 2003 knowledge base to find it.