Windows Enterprise Desktop

October 4, 2013  9:47 AM

True Win7 to Win8 Upgrade Goes Surprisingly Well

Ed Tittel Ed Tittel Profile: Ed Tittel

Almost forever, I’ve been a big proponent of the “clean install school” of Windows upgrade methodology. That is to say, rather than upgrading my systems from an older Windows version to a new one, I’ve been mostly inclined to blow away the older install in favor of a new one, followed by the added effort of reinstalling all my applications, restoring settings manually, and so forth and so on. What’s guided my activities has been the belief that this results in a leaner, more stable system, and reduced time to complete the overall installation process. And FWIW, many Windows experts — including the likes of Ed Bott, Paul Thurrott, and Woody Leonhard — have all voiced opinions or advice more or less in keeping with this approach.

Off to the races, on my way to completing an "in-place upgrade" from Windows 7 to Windows 8.

Off to the races, on my way to completing an “in-place upgrade” from Windows 7 to Windows 8.

But with the impending release of Windows 8.1 as a free upgrade for PCs already running Windows 8 on October 17/18, I’m prepping my PCs currently running Windows 7 — for which I purchased the $40 Windows 8 upgrades last year, when MS ran what still looks to be a “once in a lifetime” dirt cheap promotion to get people to move up from 7 to 8 — by upgrading them to Windows 8 in advance of the upcoming GA date. As an experiment, I’d planned to perform an in-place upgrade of my Windows 7 production desktop this weekend, with all of its 237 applications (as reported in Secunia PSI for that system) coming along for the ride.

Finding myself with some unexpected idle time yesterday afternoon, I decided to run the upgrade a bit sooner than planned. This blog post recounts my observations and experiences along the way to the successful and surprisingly smooth conclusion to that process (I’m writing this blog right now on the upgraded PC, which has shown no signs of outright weirdness or flakiness since the upgrade completed at around 5:15 PM yesterday afternoon, following about two hours of upgrade activity). I began the process by capturing two image backups of the original Windows 7 system: one using the built-in image backup captured in the Control Panel Backup and Restore utility, the other using Acronis True Image Home 2013 with the added precaution of creating a bootable UFD with the ability to restore that image to its original drive. I’d already replaced CPUID HWMonitor 1.18 with the Pro version, and uninstalled DualBootPro, Nvidia GeForce Experience, and VirtualCloneDrive to take cognizance of the pre-install warnings courtesy of the Windows 8 Upgrade Assistant beforehand.

The Upgrade tool downloaded the Windows 8 ISO from the Internet to start off the process, an activity that consumed about 24 minutes overall (I didn’t know how to point it at the local ISO copy I already had on one of my 2 TB  conventional HDs, and didn’t bother to research those details, though I do see a very good discussion of this process on Windows EightForums). This approach did have one benefit that saved me from myself, however: using the MS-provided installer I obtained when I paid for the $40 license last year apparently had the product key baked into the installer, so my oversight in neglecting to store that key on another system (it currently resides in my Outlook PST file on that very PC) didn’t impede the installation process in any way, shape, or form, to my great relief and delight. Here’s how the rest of the timeline for the overall install process shook out (all times are approximate, based on my glancing over to my laptop where I relied on its system clock for rough-n-ready timing info, rounded to the nearest minute):

00:00 – 00:24  Download Windows 8 install files from Microsoft (perhaps Akamai; source wasn’t visible)
00:24 – 00:40  Copy files and perform in-place upgrade file copy, initial installation, and configuration
00:40 – 00:44  Getting devices ready (installing device drivers is handled during this phase)
00:44 – 00:54  Getting ready (system set-up and configuration)
00:54 – 00:56  Moving your settings (importing settings and preferences from the previous Windows 7 install)
00:56 – 00:57  Finalizing your settings (adapting/customizing settings for the Windows 8 runtime environment)
00:57 – 00:59  Getting your PC ready
00:59 – 01:03  Installing apps (this means Windows 8 Store/Modern UI/Metro apps, I imagine)
01:03 – 01:05  Establishing initial log-in, switching to Windows Live account, first complete Windows 8 log-in
01:05 – 02:00  Download and install 62 updates from Windows Update to catch system up to current patch/update levels

There were six (!) reboots during this process, one during the second step above, and between each of the next three steps, with the fifth one following installing apps, and the final one after the massive update installation that concluded the overall actual upgrade process. I didn’t hit any snags along the way, nor any serious hiccups or delays. Once this process was complete, I fired up DriverAgent to observe that it now reported 5 out-of-date drivers — an interesting improvement following the upgrade, because it had reported six out-of-date drivers (all either bogus or insoluble) for the previous Windows 7 installation resident on that machine. After about one hour of downloading files and fiddling about with them, I got the number of out-of-date drivers down to one, a considerable improvement over my “healthy status” on the prior Windows installation. It is for a “motherboard resources” item in the “Disconnected Devices” section for which DriverAgent supposes that a 2010 vintage version of the Intel Extreme Tuning Utility will address the issue. However, I’ve got the latest (2013) version of that utility already installed on this PC, and because it addressed all other items related to the Intel Thermal Monitoring devices to which the out-of-date finding attaches, I’m of the opinion that this is a false negative (“bad driver”) report from DriverAgent, rather than a genuine and fixable “bad driver” report from the utility. Case closed!

Summary, Observations, and Conclusions
Now that the process is over and done with, I understand that the process of recognizing, handling, and accommodating applications adds considerably to the Windows 8 install process, and the time required to complete it. The usual 15-18 minutes for a clean install zoomed to 65 minutes or thereabouts once my sizable collection of 200-plus applications entered the picture. Soluto reports that my boot time went up from 0:55 to 1:55 following the upgrade (something that I plan to investigate and whittle away at, if I can). But otherwise, the system is running well, my applications are working (at least, all of those I’ve checked so far), and if anything, seems more stable and responsive than it did when running Windows 7. I’ve installed Start8 to help me work on the desktop more effectively (that’s where I spend 90-plus percent of my time on the system anyway), and RecImg Manager to capture Windows 8 snapshots as backups for use in the Windows 8 “Refresh your PC” facility. Since I’ll be using this system every day henceforth, count on me to report further if and when any glitches or gotchas should make themselves known to me. But “so far, so good” is how I’d sum up my experiences so far, much to my surprise.

October 2, 2013  10:46 AM

A Return to the Windows 8 Upgrade Assistant

Ed Tittel Ed Tittel Profile: Ed Tittel

I’m facing an interesting issue that I’m sure is at least somewhere on the minds of fellow Windows-focused IT professionals — namely, how well an upgrade might work from Windows 7 or Vista to Windows 8  in anticipation of the upcoming GA release of Windows 8.1 (a free upgrade to those with Windows 8 already installed on their PCs). To that end, I’m planning to bite the bullet this weekend, and try the upgrade from Windows 7 to Windows 8 on my production PC. To that end, I just re-ran the Windows 8 Upgrade Advisor to see what it could tell me about the upgrade-readiness and -worthiness of that machine. Here’s what I see after running the program, which took about one minute to run to completion on my Bloomfield vintage i7 930 based PC, with its ASUS P6X58D-E motherboard and other accoutrement.

Egad! 10 items to review. Hope it's nothing too serious...

Egad! 10 items to review. Hope it’s nothing too serious…

A click on the “See compatibility details” element reveals the following items, none of which looks distressing or even terribly serious:

Some items go away, some need updating, and some must be reinstalled. No biggie!

Some items go away, some need updating, and some must be reinstalled. No biggie!

I must say, I’m more encouraged by this result than I had initially expected to be. But in preparation for the upgrade this weekend, I’ll be making an image backup of the system as it currently stands, and also, turning it into a VM so I can keep running the same environment inside Hyper-V after the upgrade is complete, just in case — as I suspect might be more likely than this list of potential issues indicates — that some issues with the 290-odd applications I have installed on this machine might manifest after the move to Windows 8 is complete. Stay tuned: I’ll report on the results of this “big move” next Monday, October 7.

September 27, 2013  10:03 AM

More Windows 8 Weirdness: Fixing Flaky RDP

Ed Tittel Ed Tittel Profile: Ed Tittel

I’ve got a total of 5 out of 8 PCs in my house running Windows 8 now, and every now and then I encounter some new form of wacky Windows behavior that requires certain shenanigans to fix. I stumbled upon another interesting case in point yesterday, when I tried to establish a Remote Desktop Connection link to our Dell XPS12. When I got this machine from Dell it came with Windows 8 installed, which I proceeded to upgrade to Windows 8 Pro so that, among other things, I could use RDP to log into that machine remotely and manage updates and such from the production Windows 7 desktop I work at customarily in my home office.


Even though my XPS12 was properly configured for remote access, my connection wouldn’t stay up long enough to get through the hand-off process.

Without giving the matter too much thought, I checked the machine yesterday to make sure that Remote Access settings were properly configured. As shown in the preceding screencap, they were just what I thought they should have been, with remote connections turned on and RD-NLA turned off. However, when I tried to establish an RDP connection to that machine, I would start to go through the process of establishing a remote connection, only to have it fail before the entire process of opening the remote window and obtaining a working view of its desktop could complete. Non-plussed, I tried to establish a connection going the other way — that is, from the desktop of the XPS 12 to my production desktop — only to have it fail and hang in the same way. Bizarre!

By searching on “Windows 8 RDP fails during login” and “Windows 8 RDP fails immediately,” I learned two very interesting things I didn’t already know. First, I had to purge some outdated printer connections in the Devices and Printers entry in Control Panel, apparently because print queue and device driver connections were interfering with network access for RDP. And second, I had to make a registry hack to turn off the version of UDP that RDP uses in the Windows 8 environment as follows:

In the key at HKLM\SOFTWARE\Policies\Microsoft\WindowsNT\Terminal Services\Client\, create a DWORD named tofClientDisableUDP and assign the value “1” (either Hex or Decimal, I used Hex) to it.

I had to remove the printer references and then restart the machine immediately after that to get them to “stay gone,” because if I didn’t restart, they would magically re-appear within 30-60 seconds of their removal. This took some careful observation and fiddling about to achieve. I found the registry hack documented on Microsoft’s social.technet pages in a thread entitled “Remote Desktop client on Windows 8 drop connection.”

To me, it all goes to show the sometimes forensic characteristics of Window troubleshooting. I’ve learned to try to characterize the symptoms as tersely as possible, and then to put Google to work to help me find information or discussions around those topics. If I keep at it long enough, as I did yesterday afternoon, I will almost always stumble my way into a workable solution. But why, oh why, I must plaintively ask, does it have to be this way? Sigh.

September 25, 2013  4:14 PM

Windows ADK for 8.1 Now Available

Ed Tittel Ed Tittel Profile: Ed Tittel

As of the end of August, a new version of the Windows Assessment and Deployment Kit (aka the Windows ADK) is now available for Windows 8.1 (RTM version, which presumably means it will also work with the General Availability, or GA, version scheduled for release on October 16). The download page at the MS Download Center provides a link to grab the full kit for experimentation and/or production use.


The latest ADK is ready to work with the most recent RTM release of Windows 8.1 (and presumably with the GA release, too).

Here’s a list of some of the tools available in the Windows ADK (see the ADK download page for a complete list):
1. Application Compatibility Toolkit (ACT) helps IT professionals prioritize, test, and detect compatibility issues with applications, and to find and share risk assessments with other ACT users. Visit the ACT page for more information on this tool.
2. Deployment tools: a whole raft of items to help IT professionals in customizing, managing, and deploying Windows images, such as the Deployment Imaging Servicing and Management (DISM) command line utility along with numerous DISM PowerShell cmdlets and its API, the Windows System Image Manager (Windows SIM), and OSCDIMG, a command-line tool for creating an image (.iso) file of a customized 32-bit or 64-bit version of the Windows Preinstallation Environment (PE) 3.0. See the Deployment tools page for more info.
3. User State Migration Tool (USMT): a scriptable command line tool designed for migrating user data from an older Windows installation to a newer one. The USMT home page offers more information and documentation.
4. Windows Assessment Toolkit, used to run system assessments on a single computer based on tasks that simulate user activity and examine computer state to produce metrics for various aspects of the system, and make recommendations for improvement. See the Windows Assessment Toolkit home page.
5. Windows Preinstallation Environment (Windows PE) is a minimal OS created to provide a runtime environment for preparing a computer for installation and servicing of Windows OSes. The Windows PE Technical Reference is the go-to for this outstanding and valuable Windows resource.

For those who work with Windows OSes, and plan to work with or deploy Windows 8.1, the ADK is an invaluable toolset. It’s definitely well worth the time and effort needed to inspect, learn about, and master the various components it contains. At a minimum, these items provide a baseline against which other commercial toolsets must be measured, if only because MS gives them away for free.

September 22, 2013  5:15 PM

Automation Possibilities for VDI Are Endless

Ed Tittel Ed Tittel Profile: Ed Tittel

Earlier this afternoon, I finished a story for that’s currently entitled “Automation Technology in VDI Environments.” Given that it usually takes a week or two before my submissions show up online I’ll provide a link to the final version right here when it goes live (and change the title if those with editorial authority decide that something a bit different or jazzier is needed to attract reader interest). What blew me away about researching this story is the hundreds of ready-to-run scripts one can find easily online, to help automate every aspect of virtual desktop infrastructure, from initial set-up and image construction, to VM deployment, applying patches and updates, and monitoring and managing fully operational VDIs.

MS Hyper-V home page

Microsoft goes out of its way to make Hyper-V and VDI automation simple and straightforward.

All you have to do to get a sense of the massive resources available for your use are to check out these mostly Hyper-V related resources online (no surprise, really, because the vast majority of these links come from Microsoft itself, in one guise or another):

There’s lots of really great stuff here that admins are hopefully already using. If that doesn’t include you, be sure to check one or more of these items out immediately. That means today!

September 20, 2013  11:08 AM

Surface (Pro) 2 Launch on 9/23/2013 in NYC

Ed Tittel Ed Tittel Profile: Ed Tittel

Microsoft is holding an invitation only press event next Monday, September 23, to announce its new generation of Surface tablets, currently known as Surface 2. Both the RT model (to which rumors currently ascribe the label “Surface 2”) and the full-blown Windows model (to which the name “Surface Pro 2” currently sticks likewise by rumor) are supposed to get some serious upgrades. By combining interesting rumor coverage from The Verge, ZDnet, and Design&Trend, here’s what I’ve been able to piece together about the next-gen version of these devices, which appear to get about half-way to meeting the wish list I put together for the Pro model in November 2012. I’ll list what I’ve been able to learn about for each model separately, in bulleted list form (both are expected to acquire a two-step kickstand, which permits the extension to lock into two different positions rather than the current single position):

Surface 2 (Windows 8.1 RT model)

  • Slated to include a faster Tegra 4 CPU
  • RAM capacity will double, from 2 GB to 4 GB
  • Screen resolution will increase to 1080p
  • New RT OS is reportedly based on Windows 8.1, and designed to boot up, run, and shut down more quickly

Surface Pro 2 (Windows 8.1 full OS model):

  • Haswell i5 CPU, with some i7 ULV models also possible.
  • 8 GB RAM (now that one SO-DIMM accommodates 8 GB easily, this is a no-brainer).
  • 256 and 512 GB SSD configurations should be available (don’t forget: you can talk to the Microsoft Store about special-ordering higher-end models).
  • Paul Thurrott reports that battery life shold go up from 4-5 hours to as high as 7 hours (from MJF at ZDnet in her Surface Pro 2 leaks story). A new Power Cover will include a built-in, rechargeable battery pack, along with a Type Cover style keyboard, and will extend the unit’s battery life still further (by how much, however, isn’t yet known).
  • A dock for the unit is widely expected to be made available, and is said to support external monitor connections, gigabit Ethernet, plus one USB 3.0 port and three USB 2.0 ports. Sources say the dock will work with both first and second generation Surface Pro models. The dock will also charge up any attached Surface Pro tablet. No pricing information is available, though.

If the Power Cover brings the Surface Pro 2 up to 8 hours of battery life or longer, I may just find myself in the market for one. I’ll be looking forward to more detailed coverage after next week’s event concludes. Stay tuned for more info.

[Notes added 9/23/2013, based on reporting from the MS announcement:
Surface 2 (Arm version, formerly Surface RT): Tegra 4 confirmed, 4 GB RAM confirmed, higher 1080p resolution confirmed, 25% better battery life, 1xUSB3.0 port. Price starts at $499.
Surface Pro 2 (x86 version, replaces Surface Pro): MS claims 75% better battery life! 4GB RAM goes with 64 or 128 GB SSDs, 8GB with 256 or 512 GB SSDs; Power Cover said to increase total battery life to ~10 hours; Docking station supports total resolution for all screens up to 3840×2160 (equal to 2x1080p in both dimensions), adds 1xUSB3.0, 3xUSB2.0, an additional mini-DisplayPort, and GbE. Price starts at $899, but no pricing for accessories disclosed yet.
There’s even a Surface Music Kit — namely a touch cover for mixing sound instead of typing text. See the Ars Technica coverage for more details.]

[More Notes from 9/25/2013, based on Paul Thurrott’s excellent “Need to Know: Surface 2 and Surface Pro 2” article for WindowsITPro.
More complete pricing information available, especially for peripherals like the new Type Cover offerings, Power Cover, and dock, as well as for more advanced Surface Pro 2 models ($1,299 for 256 GB SSD/8 GB RAM, $1,799 for 512 GB SSD/8 GB RAM). Worth a read-through!]

September 19, 2013  10:46 AM

Microsoft recalls Office 2013 update from September Patch Tuesday

Diana Hwang Diana Hwang Profile: Diana Hwang

Microsoft’s monthly Patch Tuesday updates have started to resemble motor vehicle recalls as the company once again encounters problems after releasing a public patch update.

In the September Patch Tuesday cycle, Microsoft  recalled a non-security update dubbed KB2817630, which affected Microsoft Office 2013 and Office 2013 Pro. The update caused the Outlook 2013 folder pane to disappear.

The issue was caused by incompatibility between the outlook.exe and mso.dll files. The minimize button in the navigation pane will render very large and become invisible to the end user, thus causing it to disappear. Microsoft confirmed the issue in a blog post, where the company expressed “regret” for any inconvenience caused by this update, and explained how to address the problem.

For Microsoft and its pursuit of a rapid release cadence for updating software, the latest mishap with the Patch Tuesday updates might be cause for concern.

The company recently pulled several patches off its sites and offered band aid fixes. In August, Microsoft pulled the MS13-061 Exchange security update and reissued an update later in the month. In April, the company recalled security update MS13-036, which affected Windows 7 and Windows Server 2008 R2 end users, and re-released it later in the month.

The recent string of patch issues serve as a reminder to IT pros to implement them with care.

“The rule has always been to test out patches before deploying widely, and it appears that administrators have been letting that best practice lapse,” said Eric Beehler, an IT professional who offers consulting and training services with Consortio Services LLC, of Colorado Springs, Colo. “Admins just need to reset their best practices and always have their rollback plans ready, just in case.”

September 18, 2013  1:51 PM

Microsoft ships Windows 8.1 Enterprise RTM

Diana Hwang Diana Hwang Profile: Diana Hwang

Microsoft is finally giving its bread and butter enterprise customers the ability to download Windows 8.1 Enterprise RTM through its TechNet and MSDN subscriptions.

Volume licensing customers also will be able to download the new RTM if they have an active Software Assurance (SA) agreement.

Just last week, Microsoft had to reverse its stance on giving out Windows 8.1 RTM bits to IT pros and developers. Windows developers who caused an uproar were particularly upset at being left out of the initial Windows 8.1 RTM release to PC manufacturers.

A Microsoft spokesperson said after the Windows 8.1 RTM was made available to TechNet and MSDN subscribers there were code reviews and other processes that needed to occur before releasing additional products to the public.

If Microsoft wants to court enterprise customers and encourage them to test Windows 8.1 in their organizations, they need to make sure all the pieces are available to IT professionals and simply communicate their intention.

All they had to do was explain that they planned to do a phased approach for releasing the various versions of Windows 8.1 RTM. First Windows 8.1 RTM will go to the PC manufacturers, then to IT pros and developers and finally, Windows 8.1 Enterprise RTM for volume licensing customers who have an active SA agreement.

Had Microsoft communicated this approach, it would have suffered a lot less backlash from the industry. Hopefully Microsoft learned some lessons from this experience.

On a separate note, if you don’t have an MSDN or TechNet subscription and need to wait until October 18 to get a commercial copy of Windows 8.1, Microsoft released the list pricing for those who don’t qualify for a free upgrade.

Windows 8.1 will cost you $119.99 and Windows 8.1 Pro will cost $199.99. And here’s some other pricing. For those who are thinking of buying a new Windows 8.1 device too, you can upgrade your Windows 8.1 operating system the Pro Pack version that includes Media Center for $99.99. If you are planning to buy Windows Pro 8.1, you can add-on the Media Center for $9.99.

September 18, 2013  10:40 AM

MS Shares Pricing Info for Windows 8.1

Ed Tittel Ed Tittel Profile: Ed Tittel

Thanks to a report from Mary Jo Foley at ZDNet that posted yesterday, I can now tell you how much Windows 8.1 will cost those who wish to upgrade from a version of Windows earlier than 8.0 to Windows 8.1. For Windows 8.0 users that upgrade will be free, but others must pay for the privilege of moving up to Windows 8.1. Those running Windows XP, Vista, or Windows 7 will pay $119.99 to upgrade to plain-vanilla Windows 8.1, or $199.99 to upgrade to Windows 8.1 Pro. Those prices are the Microsoft list prices (MSRP, as it were, and of course thus also what the Microsoft Store will be charging) and apply both to digital downloads and to retail-packaged boxed versions with DVDs sold at big box stores around the world. As MJF observes in her story, “these are the same prices Microsoft charged users of older versions of Windows for the Windows 8 and Windows 8 Pro upgrades.”


A snapshot of the new retail package (box) for Windows 8.1, courtesy of MJF and MS.

This time around, however, there will be some differences vis-a-vis the last set of downloads and boxed products that MS offered for Windows 8.0 versus 8.1:

  • The boxed version incorporates a “full-version” installer. In plain English, that means even though it’s called an upgrade, you can still use it to perform a bare-metal install on a brand-new machine with no prior OS to upgrade from. I had been puzzled why MS hadn’t mentioned anything about a separate full-version SKU (which usually costs more than an upgrade-only SKU) but now we all know that the upgrade is also a full-version so there’s no need to buy (or pay extra for) a different version for that purpose. This is great news for those who build their own systems, or who want to blow away their boot/system drives completely to perform what you might jokingly call a “squeaky-clean install!”
  • Those who move from Windows 7 to 8.1 may indeed be able to perform an “upgrade install” but they won’t be able to bring their desktop apps along for that ride. For the first time ever, MS will require a fresh re-install of desktop apps following an upgrade install  from 7 to 8.1 (bummer!).
  • MS recommends that those with PCs running XP or Vista skip the upgrade install completely, and perform a clean install instead. MJF provides this explanation “older hardware plus Winodws 8.1 won’t make for an optimal experience” and says that “Microsoft is advising them to buy the retail DVD, rather than download the bits and boot from the DVD to do a clean install…”
  • Users who purchase new hardware running Windows 8.1 will be able to buy a Windows 8.1 Pro Pack from MS for $99.99, to add support for Pro features along with Windows Media Center. Users already running Windows 8.1 Pro can buy Windows Media Center for $9.99.
  • There are no current plans to offer limited-time savings on Windows 8.1 upgrades. For some time after Windows 8.0 went into General Availability (the GA release on October 26, 2012), anybody who owned a copy of XP, Vista, or Windows 7 was able to purchase an upgrade to Windows 8 for a paltry $40. It doesn’t look like they’re going to repeat that offer, alas.

September 16, 2013  10:41 AM

Windows 8.1 Upgrade Gone Awry Teaches Valuable Lesson

Ed Tittel Ed Tittel Profile: Ed Tittel

Having successfully upgraded a test machine to Windows 8.1 on Friday, I decided to do likewise to my son’s brand-new state-of-the-art Dell XPS 27 All-in-One which showed up at the house about three weeks ago. It is the only system at my disposal new enough to have come with Windows 8 already installed, and I wanted to see how the whole upgrade experience would go on that machine. Much to my later surprise, upon reflection as to why my attempts failed, initial screening of suitability (the compatibility check phase of the pre-install maneuvers now built into the Windows Installer) failed to determine that the Atheros/Qualcomm Killer-N 1202 wireless network interface built into that machine doesn’t work with Windows 8.1. I also experienced some interesting display and storage issues in trying to make the upgrade (and then a clean install) work, which resulted in two pretty major hurdles to the 8.1 install process:


The XPS 27 Haswell model is fast and surprisingly capable, but the Atheros Killer-N 1202 wireless adapter,
Intel HD 4600 display, and RST-based storage environment all impacted
(and ultimately foiled) my attempts at a Win8.1 upgrade — for now, anyway.

1. On the display side, something with the Intel HD 4600 graphics chip went wonky, which resulted in constant (and highly irritating) on-off behavior for the built-in 27″ display. I solved the irritation part by covering the display with a towel, and found that attaching an external monitor via the unit’s HDMI-Out port (a Dell 23″ monitor, as it turns out) worked just fine.
2. On the storage side, I had to load an AHCI driver from the Dell Driver disk that shipped with the unit, to permit the Windows 8 installer to see the primary hard disk (which depends on Intel RST to gang up the built-in 32 GB mSATA SSD and a conventional 2 TB HD to provide access to the built-in storage subsystem on the XPS 27 AIO)

After part-installing Windows 8.1 on the machine, I had a PC that would boot but with no network access capability, and seriously wonky display behavior, it turned out to be simply unnacceptable for everyday use. After spending three hours trying various repair methods (including routing a 100 ft Cat 5 cable from my downstairs network switch to the GbE interface on the back of the unit) I had to give up on installing Windows 8.1 on that machine. I was able to completely reformat the primary drive after supplying the right AHCI driver during the initial install process in performing a clean re-install of Windows 8.0, and by using the external monitor got past initial installation to the point where I could install the proper HD 4600 video driver to return the display to its usual, brilliant and rock-solid graphics performance.

After that, it was just a matter of applying updates to the base-level OS (around 60 of them altogether: 52 immediately following installation, and another 6-8 as various applications and services brought .NET and Silverlight into the runtime picture), addressing the out-of-date device drivers (more or less the same 19 I ran into on my Windows 8.1 upgrade from Friday on a different machine, interestingly enough), and re-installing my usual collection of tools and utilities (RecImg Manager, CCleaner, 7-Zip, WinDirStat, WSCC, and CPU-Z went on right away, and I’ll probably keep adding more in dribs and drabs over the next week or two, as I continue to work on that machine in my spare time).

And obviously, I’m going to keep my eyes on the XPS 27 support pages on the Dell site, so that when the driver issues get resolved, I can try the upgrade “once more, with feeling!”

Forgot Password

No problem! Submit your e-mail address below. We'll send you an e-mail containing your password.

Your password has been sent to: