windows_7_banner

It is always cool to find a bug in software. Whether it is an ATM, movie ticket machine, or Windows we all feel a certain sense of pride in identifying something that doesn’t work like we think it should. Windows is a product of a lot of people, not just those of us at Microsoft. When something isn’t as it should be we work with a broad set of partners to make sure we can effectively work through the issue. I hope folks recognize how serious we take this responsibility as we all know we’re going to keep looking at issues and we will have issues in the future that will require us to change the code to maintain the level of quality we know everyone expects of Windows. – Engineering Windows 7

Most people that read this site will remember last week when there was a “Show Stopper” Windows 7 bug that was uncovered. I as well as others have verified that there is in fact a bug with Check Disk that consumes excess system memory however a more serious side affect was reported, system crashes. I was never able to get my system to crash but was able to confirm that the bug itself did exist as far as it relates to memory.

There has been a lot of speculation as to just how Microsoft was going to respond to this issue and thankfully they have responded via the Engineering Windows 7 blog. The response is best summarized as “We are aware of the memory issue but have not been able to replicate it crashing”. The interesting part is not that they were unable to replicate the crash but that they go in depth as to how they approach this type of reported bug.

Obviously the Windows 7 team has got it together when it comes to tackling bugs and it is nice to see that even after it went RTM they are working with the community to track down every little problem.

Check It Out> Engineering Windows 7 Blog