JustForex
Loading recent posts...

Nov 7, 2011

Windows 7 SP1 Fix – Copying 40GB of Data to a Blu-Ray Disk May Take Over 3 Days and Can Crash If Command Prompt Is Opened and Closed Repeatedly




Windows 7 SP1 Fix – Copying 40GB of Data to a Blu-Ray Disk May Take Over 3 Days


Microsoft is providing a fix to customers which have experienced problems when copying large amounts of data to a Blu-Ray disk on their Windows 7 computers.
According to the software giant, extremely poor performance is the indicator that users might have a problem.

The Redmond company reveals that copying over 10 GB of data to a Blu-Ray can take more than a day to complete, and even several days, depending on the size of the job.

Windows 7 customers can find that they’re affected, as can those with Windows Server 2008 R2. Upgrading to Service Pack 1 won’t solve this problem for either.

“Assume that you try to copy more than 10 gigabytes of data to a Blu-ray disk on a computer that is running Windows 7 or Windows Server 2008 R2. In this situation, the copy operation takes more than one day to finish,” Microsoft reveals.

“For example, you try to copy 40 gigabytes of data to a Blu-ray disk on a computer that is running Windows 7. In this situation, it may take more than three days to copy the data. However, this operation only takes about 12 hours on a computer that is running Windows XP.”

Another symptom detailed by Microsoft involves customers operating system dual Blu-ray disc drives on their machines. The second disc drive fails during the copy operation, the Redmond company notes.

The software giant already identified the source of the glitch, noting that:

“This issue occurs because of redundant error checking in the Universal Disc File System driver (Udfs.sys) code. This behavior slows the speed of the write operation after a specific amount of data is written to the disc.”

Not only this, but a hotfix is already available for download from Microsoft Support, with the Redmond company promising that it will be included into the second service pack for Windows 7 and Windows Server 2008 R2.







Windows 7 SP1 Can Crash If Command Prompt Is Opened and Closed Repeatedly


It might be less of a good idea to repeatedly open and close a command prompt or a PowerShell console in Windows 7, than you might think, at least according to Microsoft.
The Redmond company reveals that launching and exiting either a command prompt or a PowerShell console multiple times can generate potential problems, and even crash the operating system.

Windows Server 2008 R2 is also affected by this issue, as are the versions of the two platforms that have already been upgraded to Service Pack 1 (SP1).

If customers indeed go ahead and perform the actions described above, Microsoft warns that “the performance of the computer may become slow, and applications may crash.”

Still, the problem is not generalized, as it “occurs when you use a non-English input method (such as the Japanese IME),” Microsoft added.

Apparently, at fault for the poor performance and for the potential crashes are Graphics Device Interface (GDI) objects, which get leaked for every open / close action.

“The leak occurs in the Taskhost.exe process or the Explorer.exe process, depending on whether the language bar is displayed or not. When the number of leaked GDI object handles in the process reaches the maximum number, no more GDI objects can be created,” Microsoft explains.

“When an application receives the focus for the first time, a notification is sent to all language bars. Then, the language bars allocate GDI objects for the application. However, when a command prompt or a PowerShell console is closed, the Conhost.exe process does not send a notification to clean up the GDI objects that were allocated by the language bars. Therefore, the leak occurs.”

Microsoft details the issue in KB2617157, and this article is also the best place for customers to find and download a fix.

The hotfix is available directly from Microsoft support, but users should only deploy it if they are indeed impacted by the glitch described above. Otherwise, they should wait for Windows 7 SP2, which apparently will also pack this hotfix.

0 comments:

Post a Comment

Twitter Delicious Facebook Digg Stumbleupon Favorites More

 
Design by Free WordPress Themes | Bloggerized by Lasantha - Premium Blogger Themes | coupon codes
`