2013年6月20日星期四

Windows 8: Now is the time for business to get onboard

Now is the time for businesses to consider deploying Windows 8 on office PCs, according to analyst house Gartner.

Firms considering deploying Windows 8.0 on tablets, or other touchscreen devices, should evaluate "broader deployment" of the OS to desktop and laptop PCs following the upcoming release of Windows 8.1, Gartner advises.

The 8.1 release will address criticisms about the usability of Windows 8 new tile-based interface, which some users of older Windows systems found confusing. The update will bring back the Start Button and make other UI tweaks, as well as introducing the ability to boot to the desktop and Internet Explorer 11.

"Some users rejected Windows 8 because of the changes Microsoft made, coupled with a lack of discoverability, help or cues for the new user experience," according to the post written by Michael Silver and Steve Kleynhans, vice presidents in Gartner's client computing team.

"Based on information currently available, Gartner believes Windows 8.1 features could quiet most of its detractors."

Windows 8 had been installed on fewer than one in 20 PCs and tablets as of the end of May this year, according to figures from web analytics firm Net Applications.

Businesses engaged in planning Windows 8 deployments should pilot on Windows 8.0 if it makes sense, but switch to the Windows 8.1 beta as soon as possible and plan to use Windows 8.1 for production deployments, Gartner says.

Gartner predicts changes in 8.1 will not break compatibility with most legacy Windows applications, but warns to expect "compatibility issues" when moving from IE8 to IE11.

Businesses using Windows 8 should expect more updates like 8.1 on an annual basis, it advises.

The final version of Windows 8.1 is due before the end of the year and will be delivered free to all Windows 8 and Windows RT users through the Windows Store.

2013年6月14日星期五

Windows 8 update bug clogs CPUs

Released earlier this week as part of the company's monthly Patch Tuesday update cycle, KB2821895 is designed to update the servicing stack - the portion of the operating system used by Windows Update - to add much-needed improvements. Among the features tweaked or added by the update are the ability to install previously downloaded updates without an active internet connection, a reduction in certain software sizes, and the automatic compression of unused binary files when updates are installed.

While many of the new features are targeted more at tablet users than desktop users, the update was released to all Windows 8, Windows RT and Windows Server 2012 users on Tuesday. Sadly, it soon transpired that there was a problem: with the update installed, users began to report that processes related to the analysis of system files - in particular the TiWorker.exe application, part of the Microsoft System File Checker tool - would take up masses amounts of processor time, locking cores with between 40 and 100 per cent utilisation until failing with an error.

During this time, a logfile - CBS.log - is seen to rapidly grow with entries that show files being marked as damaged, then unable to be repaired. These files, however, do not appear to be actually damaged, and the system runs as normal - albeit slowly - while the error is occuring.

Not everyone who has installed the patch has reported the problem, and thus far it's not clear what is causing the issue on systems that are affected. With KB2821895 not valid for uninstallation, however, a workaround is needed for those that are suffering from the glitch - and, thankfully, there is one.

According to a member of the German-language Dr. Windows forum, which was one of the first sites to spot the problem, the issue can be solved by running the Deployment Image Servicing and Management (DISM) command below with administrative privileges:

DISM /online /cleanup-image /restorehealth

While this process takes some time, it should prevent the CPU from being overloaded with spurious analysis and error logging. Thus far, Microsoft has not commented on the flaw in the update, nor has it indicated any plans to release a patch of its own for the issue.