# Email hassles with migration to Windows 10 – if you use Windows Live Mail

Scenario: you are using Windows 7 and for email, Windows Live Mail, Microsoft’s free email application. You PC is getting old though, so you buy a new PC running Windows 10, and want to transfer your email account, contacts and old messages to the new PC.

Operating systems generally come with a built-in mail client, and Windows Live Mail is in effect the official free email client for Windows 7. It was first released in 2007, replacing Windows Mail which was released with Vista in 2006. This replaced Outlook Express, and that evolved from Microsoft Mail and News, which was bundled with Internet Explorer 3 in 1996. Although the underlying code has changed over the years, the user interface of all these products has a family resemblance. It is not perfect, but quite usable.

Windows 8 introduced a new built-in email client called Mail. Unlike Windows Live Mail, this is a “Modern” app with a chunky touch-friendly user interface. Microsoft declared it the successor to Windows Live Mail. However it lacks any import or export facility.

The Mail app in Windows 10 is (by the looks of it) evolved from the Windows 8 app. It is more intuitive for new users because it no longer relies on a “Charms bar” to modify accounts or other settings. It still has no import or export feature.

The Mail app is also not very good. I use it regularly now myself, because there is an account I use which works in Mail but not in Outlook. I don’t like it. It is hard to articulate exactly what is wrong with it, but it is not a pleasure to use. One of the annoyances, for example, is that the folders I want to see are always buried under a More button. More fundamentally, it is a UWP (Universal Windows Platform) app and doesn’t quite integrate with the Windows desktop as it should. For example, pasting text from the clipboard is hilariously slow and flashes up a “Pasting” message in an attempt to disguise this fact. Sometimes it behaves oddly, an open message closes unexpectedly. It is like the UWP Calculator app, another pet hate of mine – I press the Calculator key on my Windows keyboard, up comes the Calculator, then I type a number and it doesn’t work, I have to click on it with the mouse before it accepts input. Just not quite right.

I am getting a little-off topic. Back to my scenario: how are you meant to transition from Windows Live Mail, the official mail client for Windows 7, to the Mail app in Windows 10, if there is no import feature?

In one way I can explain this. First, Microsoft does not really care about the Mail app. Everyone at Microsoft uses Outlook for email, which is a desktop application. This is important, because it means there is no internal pressure to make the Mail app better.

Second, Microsoft figures that most people now have a cloud-centric approach to email. Your email archive is in the cloud, so why worry about old emails in your Mail client?

This isn’t always the case though. A contact of mine has just been through this exact scenario. He has happily used Windows Live Mail (and before that Outlook Express) for many years. He has an archive of old messages which are valuable to him, and they are only in Windows Live Mail.

Unfortunately Microsoft does not currently have any solution for this. The answer used to be that Windows Live Mail actually works fine on Windows 10, so you can just install it. However Microsoft has declared Windows Live Essentials, of which Live Mail is a component, out of support and it is no longer available for download.

Incidentally I am writing this post in Windows Live Writer, another component of Essentials, but which fortunately has been published as open source.

If you can find the Windows Live installation files though, it still runs fine on Windows 10. You do need the full setup, called wlsetup-all.exe, rather than the web version which downloads components on demand. Here it is, installed and connected on Windows 10:

This application is no longer being maintained though, and there are some compatibility issues with some email services. This will get worse. The better answer then is to migrate to full Outlook. However, Microsoft makes Outlook expensive for home users, presumably to protect its business sales. Office Home and Student does not include Outlook, and to buy it separately costs more, currently £109 in the UK. Another option is to subscribe to Office 365 and pay a monthly fee.

Even if you intend to migrate to Outlook eventually, it may make sense to use Live Mail for a while on Windows 10. There is an export option to “Exchange” format which means you can migrate messages from Live Mail to Outlook.

This is all more work than it should be, for what must be a common scenario. You would think that migrating from the official mail client for Windows 7, to the official mail client for Windows 10, would not be so difficult.

# How to overcome “A required drive partition is missing” in Windows 8.1 reset

Here is the scenario: an HP all-in-one PC gets a virus and as a precaution the owner wishes to reinstall Windows.

The recovery drive on the PC is intact, but attempting to use the Windows 8.1 troubleshooting tools to “Reset your PC” (in effect reinstalling Windows) raises the error “A required drive partition is missing”.

This seems to be a common scenario in cases where the PC was supplied with Windows 8 and upgraded to Windows 8.1. The problem seems to be that Windows 8.1 makes some changes to the drive partitions that make it incompatible with the Windows 8.0 recovery partition.

Here is the workaround I used:

1. In Windows 8.1, make a recovery drive. To do this, first connect a USB drive that you are happy to have wiped. It will need a capacity of around 16GB or more. Then run Control Panel, search for “recovery”, and choose Create a recovery drive.

2. When creating the recovery drive, make sure the option to include the recovery partition is checked. This will copy the recovery partition from the PC to the USB drive.

3. When you are done, you will be able to boot from the USB drive. You could choose the Reset option from there, however you will still get the error. First, go to Troubleshooting and Advanced and select the command prompt. When the command prompt opens, type:

diskpart

Now type:

list disk

You will see two disks (or more) listed, one for the USB boot device, and the others the disk(s) in the PC. Select the internal boot drive. It is normally obvious from the sizes which is which. Select it by typing:

select disk n

where n is the number of the drive as shown by list disk.

WARNING: the next step will delete all data on the selected drive. If in doubt, back out and make a backup of the drive before proceeding. If something goes wrong, your PC will no longer be bootable and you will need recovery media from the manufacturer, or to buy a new copy of Windows.

Once you are happy that it is safe to delete everything from the drive, type:

clean

or

clean all

The first command does a quick removal of the partition table from the drive but does not zero the data; it will be invisible but possibly recoverable using data recovery tools. The second command zeroes all the data and takes much longer (several hours), but it is more secure, if for example you want to sell or transfer the PC.

Once this is done,reboot the PC using the USB recovery drive. Select troubleshooting, then Reset your PC. This time it will work and you will be back in Windows 8.0.

Note: This scenario is common enough that it seems to be a flaw in the Windows 8.x recovery tools. I do not understand why Microsoft has so little regard for its users attempting to recover Windows (and usually highly stressed) that it has not fixed this problem.

Note 2: What if you cannot boot into Windows 8.1 to make the recovery drive? I have not tried it, but in theory it should be possible to create a recovery drive on another PC and copy the recovery drive to it.

# Quick thoughts on Surface 3 from a long-term Surface user

I’ve been using a Surface as my usual travel PC for a while now – mostly Surface Pro (the first iteration) but also Surface RT and Surface 2. Microsoft has announced Surface 3 – is that a good buy?

Note: this is not a review of Surface 3. I intend to review it but have yet to get my hands on one.

First, a quick note on how I have got on with Surface to date. I love the compact size of the devices and the fact that I can do all my work on them. I find full-size laptops unbearably bulky now – though slim ultrabooks or small netbooks still have some appeal.

The main annoyances with my Surface Pro are the small SSD size (I have the 128GB model) and a few technical difficulties, mainly that the keyboard cover (currently the Power Cover) plays up from time to time. Sometimes it stops responding, or I get oddities like the mouse pointer going wild or keys that auto-repeat for no reason. Detaching and re-attaching the keyboard usually fixes it. Given that this is Microsoft hardware, drives and OS, I regard these bugs as disappointing.

Surface power handling is not very good. The Surface is meant to be running all the time but sleeps so that touching power turns it on or off almost instantly. That’s the idea, but sometimes it fails to sleep and I discover that it has been heating up my bag and that the battery is nearly flat. To overcome this, and to save battery, I often shut it right down or use hibernate. Hibernate is a good option – fairly quick resume, no battery usage – except that about every third resume it crashes. So I tend to do a full shutdown.

I find the power button just a little unpredictable. In other words, sometimes I press it and nothing happens. I have to try several times, or press and hold. It could be the contact or it could be something else – I don’t think it is the contact since often it works fine.

The power cover has stopped charging, after 10 months of use. It is under warranty so I plan to get it replaced, but again, disappointing considering the high cost ($199). A few grumbles then, but I still like the device for is portability and capability. Surface Pro 2 seemed to be better that the first in every way. Surface Pro 3 I had for a week on loan; I liked it, and could see that the pen works really well although in general pens are not for me; but for me the size is a bit too big and it felt more like an ultrabook than a tablet. What about Surface 3 then? The trade-off here is that you get better value thanks to a smaller size (good) and lower performance (bad), with an Atom processor – Intel’s low power range aimed at mobile computing – instead of the more powerful Core range. Here are some key stats, Surface 3 vs Surface Pro 3:  Surface 3 Surface Pro 3 Display 10.8″ 12″ Weight (without cover) 622g 800g Storage 64GB or 128GB 64GB-512GB Processor Intel Atom x7 Intel Core i3, i5 or i7 RAM 2GB or 4GB 4GB or 8GB Pen Available separately Included Cameras 8MP rear, 3.5MP front 5.0MP rear, 5.0MP front What about battery life? Microsoft quotes Surface Pro 3 as “up to 9 hours of web browsing” and Surface 3 as “up to 10 hours of video playback”. That is a double win for Surface 3, since video playback is more demanding. Anandtech measured Surface Pro 3 as 7.6 hrs light use and 3.45 hrs heavy use; the Surface 3 will fare better. How much do you save? A snag with the Surface is that you have to buy a keyboard cover to get the best out of it, and annoyingly the cover for the Surface 3 is different from those for Surface, Surface 2 and Surface Pro, so you can’t reuse your old one. A quick look then at what I would be paying for the Surface 3 vs Surface Pro 3 in a configuration that makes sense for me. With Surface 3, I would max out the RAM and storage, because both are rather minimal, so the cost looks like this: Surface 3 with 4GB RAM and 128GB storage:$599
Keyboard cover: $129 Total:$728.99

Surface Pro 3 with 8GB RAM, 265GB storage, Intel Core i5, pen: $1299 Keyboard cover:$129.00
Total: $1428.99 In other words, Surface 3 is around half the price. Will I buy a Surface 3? It does look tempting. It is a bit less powerful than my current Surface Pro and perhaps not too good with Visual Studio, but fine for Office and most general-purpose applications. Battery life looks good, but the 128GB storage limitation is annoying; you can mitigate this with an SD card, say another 128GB for around$100, but I would rather have a 256GB SSD to start with.

However, there is strong competition. An iPad Air, I have discovered, makes an excellent travel companion, especially now that Office is available, provided you have a good keyboard case such as one from Logitech; you could get an iPad Air 2 with 64GB storage and a keyboard for slightly less than a Surface 3.

The iPad comparison deserves some reflection. The iPad does have annoyances, things like lack of direct access to the file system and non-expandable storage (no USB). However I have never encountered foibles like power management not working, and as a tablet it is a better design (not just because there are abundant apps).

It is also worth noting that there is more choice in Windows tablets and convertibles than there was when Surface was first released. Some are poorly designed, but ranges like those from Asus and Lenovo are worth checking out. In a sense this is “job done” since one of the reasons for Microsoft doing Surface was to kick-start some innovation in Windows hardware.

I hope to get some hands-on with Surface 3 in the next few weeks and will of course report back.

# Restoring a system image backup on Windows 7 when system recovery fails

I was asked to look at a laptop over the weekend. It was an HP running Windows 7 Home Premium, and the user was having problems installing applications. I noticed several things about it:

• Lots of utilities like registry cleaners, system care, driver accelerator and more were installed
• When I tried to remove the third-party firewall and use the Windows firewall instead, the Windows firewall could not be fully enabled
• Most applications could not be removed using Control Panel – Programs and Features
• Right-clicking a network connection and choosing Properties gave an error

When Windows is in this kind of state it makes sense to reinstall from scratch. There was an intact recovery partition, so I backed up the data and ran system recovery. This seemed to go fine until right at the end, when it gave an error and invited me to contact HP support. Oddly, if I chose HP’s “Minimized Image Recovery” I still got an error, but it got me a working “Windows Basic” installation, but Windows Basic is not much use because of some arbitrary limitations Microsoft imposed.

Now I had a problem, in that the system recovery had successfully removed the old Windows install, but had failed to install a new one.

One solution would be to re-purchase Windows or try to get recovery media from HP, but before going down that route, I decided to use a system image backup that had been made earlier. There was a backup from a year or so ago on a USB hard drive. I booted using a Windows 7 DVD, chose Repair your computer, then System Image Recovery.

Unfortunately Windows refused to list the backed up system image, even though it was in the standard location under WindowsImageBackup. Since the backup was not listed, it could not be restored.

Fortunately there is another approach that works. A system image backup actually created a virtual hard drive (.vhd) for each of the drives you select. You can zap the contents back onto the real hard drive to restore it.

This HP has three partitions. One is a small system partition used for booting, one is the main partition (C drive) and one is the recovery partition. The main partition is the one that matters. Here is what I did.

First, I installed Drive Snapshot, a utility I’ve found reliable for this kind of work.

Next, I plugged in the USB drive and found the .vhd file. These are located in WindowsImageBackup\[NAME OF PC] and have long names with letters and numbers (actually a GUID) followed by .vhd. The old C drive will be the largest file (there are usually at least two .vhd files, the smaller one being the system partition).

Step 3 is to mount the vhd so it looks like a real drive in Windows. You do of course need a working Windows PC for this; even Windows Basic will do, or you can use a spare PC. I opened a command prompt using Run as administrator and ran DISKPART. The commands are:

select vdisk file=”path\to\vhd\filename.vhd”

attach vdisk

I generally leave DISKPART open so you can detach the vdisk when you are done.

When you enter “attach vdisk” an additional drive will appear in Windows Explorer. This is your old drive. You can copy urgent documents or data from here if you like.

The goal though is to restore your PC. Run Drive Snapshot or an equivalent utility.

Choose Backup Disk to File. Select your old drive and back it up to an external USB drive. I hesitate to mention it, but you also need to keep the drive with the .VHD on it attached for obvious reasons! You can back up to that same drive if there is room.

Once complete, go back to DISKPART and enter:

detach vdisk

Now you need to use Drive Snapshot to restore your old hard disk. I was lucky in this case; I could run the utility in Windows Basic on the laptop itself and restore it from there. Drive Snapshot is smart enough that you can even restore the drive where it is running, after a reboot. You could also use pretty much any old version of Windows, no need to activate it, just to run the utility.

After the restore I was able to boot Windows and all was well, apart from the hundreds of Windows Updates needed for an OS that was a year out of date. In some cases though you might need to go back into system recovery to repair the boot configuration; it usually does that pretty well.

# Why Microsoft is hard to love

Microsoft CEO Satya Nadella stated last week that “We want to move from people needing Windows to choosing Windows to loving Windows. That is our bold goal with Windows.”

It is an understandable goal. Many users have discovered a better experience using a Mac than with Windows, for example, and they are reluctant to go back. I will not go into all the reasons; personally I find little difference in usability between Mac and Windows, but I do not question the evidence. There are numerous factors, including the damage done by OEMs bundling unwanted software with Windows, countless attacks from malware and adware, badly written applications, low quality hardware sold on price, and yes, problems with Windows itself that cause frustration.

There is more though. What about the interaction customers have with the company, which makes a difference to the emotional response to which Nadella refers? Again, Apple has an advantage here, since high margins enable exceptional customer service, but any company is capable of treating its customers with respect and consideration; it is just that not all of them do.

Now I will point Nadella to this huge thread on Microsoft’s own community forums.  The discussion dates from September 10 2014 and the contributors are customers who own Windows Phone devices such as the Lumia 1020. They discovered that after updating their devices to Windows 8.1 they experienced intermittent freezes, where the phone stops responding and has to be cold booted by pressing an emergency button combination (volume down plus power). These, note, are critical customers for Microsoft since they are in the minority that have chosen Windows Phone and potentially form a group that can evangelise this so far moribund platform to others.

The thread starts with a huge effort by one user (“ArkEngel”) to document the problem and possible fixes. Users understand that these problems can be complex and that a fix may take some time. It seems clear that while not all devices are affected, there are a substantial number which worked fine with Windows Phone 8, but are now unreliable with Windows Phone 8.1. A system freeze is particularly problematic in a phone, since you may not realise it has happened, and until you do, no calls are received, no alerts or reminders fire, and so on, so these customers are anxious to find a solution.

Following the initial complaint, more users report similar issues. Nobody from Microsoft comments. When customers go through normal support channels, they often find that the phone is reset to factory defaults, but this does not fix the problem, leading to multiple returns.

Still no official comment. Then there is an intervention … by Microsoft’s Brian Harry on the developer side. He is nothing to do with the phone team, but on 27 October receives this comment on his official blog:

Brian, sorry to hijack you blog again, but you are the only person in MS who seems to care about customers. Can you please advise whoever in MS is responsible for WP8.1 and make them aware of the “freeze” bug that MANY users are reporting (31 pages on the forum below). There has been NO feedback from MS whatsoever in the months that this has been ongoing and it is obviously affecting many users (myself included). If “cloud first, mobile first” is to be a success, you better make the bl00dy OS work properly. Thanks

Harry promises to raise the issue internally. On 12 Nov still nothing, but a reminder is posted on Harry’s blog and he says:

Nag mail sent.  Sorry for no update.

This (I assume) prompts a post from Microsoft’s Kevin Lee – his only forum post ever according to his profile:

I’m sorry we’ve been dark – I work closely with the Lumia engineering team that’s working directly on this. Trying to shed a little light on this…

Beginning in early September we started to receive an increased number of customer feedback regarding Microsoft Lumia 1020 and 925 device freezes. During the last two months we have been reaching out for more and more data and devices to systematically reproduce and narrow down the root cause. It turned out to be a power regulator logic failure where in combination with multiple reasons the device fails to power up the CPU and peripherals after idling into a deep sleep state.

I am pleased to pass on that we have a fix candidate under validation which we expect to push out the soon with the next SW update!

OK, so Microsoft knows about the problem, has sat back saying nothing while users try this thing and that, but now after two months says it has a “fix candidate”. This is greeted warmly as good news, but guess what? Phones keep freezing, no fix appears, and in addition, there is lack of clarity about how exactly the fix is being “pushed out”.

Two months later, user Shubhan NeO says:

And I broke my Lumia 1020. Not going back to Windows Phone ever ! Switching back to Android ! Here is sneak peek of my phone !

It is not quite clear whether he broke the phone deliberately in a fit of frustration, but perhaps he did as he comments further:

Works ? Seriously ? It hangs 2-3 a day, has stupid support for official apps. So many issue.

I’m done.

Here is another:

I paid the extra £ for a better phone; with a better ’41-megapixel camera’… now to find out that people with cheaper models have not had any freeze problems. Despite peoples comments about this being an aged device, and probably the reason for lack of support, I must add that I only purchased my 1020 ‘NEW’ in July 2014 (which is only 6 months ago). For 3 of those months it has been very unreliable … I am extremely disappointed in how I and everyone else here has been treated by Microsoft.

What are the real problems here? The hardest thing to accept is not the fact of the fault occurring, or even the time taken to fix it, but the apparent lack of concern by the company for the plight of its customers. If Mr Lee, or others from the team, had posted regularly about what the problem is, how they are addressing it, possible workarounds and likely time scales, it would easier for users to understand.

As it is, it seems that this part of the company does not care; a particular shame, as Nokia had a good reputation for customer service.

I post this then as feedback to Nadella and suggest that a cultural shift in some areas of Microsoft is necessary in order to make possible the kind of emotional transition he seeks.

# Microsoft’s Lumia 400, the cheapest Windows Phones yet, but what is the brand becoming?

Microsoft has announced the Lumia 435, the first 400-series Lumia and the cheapest Windows Phone yet. The Lumia 532, also just announced, is an upgrade to the Lumia 530 and also pitched at a low-end market.

Lumia 432

The 435 has a dual-core 1.2GHz Snapdragon processor, 1GB RAM and 8GB storage, front-facing camera, back-facing 2MP camera, micro SD slot. 4″ 800 x 480 pixel screen. GPS, wi-fi and Bluetooth. Replaceable battery. Dual-SIM is available.

The 532 has a quad-core 1.2 GHz Snapdragon processor, 1GB RAM and 8GB storage, 5.0MP main camera, front-facing camera, micro SD slot. 4″ 800 x 480 pixel screen. GPS, wi-fi and Bluetooth. Replaceable battery. Dual-SIM is available.

The phones are expected to go on the market in February at a price of around €69 (£53.50) for the Lumia 435 and €79 (61.50) for the Lumia 532.

I like the Windows Phone OS, and these devices look like great value. That said, the last aspirational Windows Phone was the Lumia 1020 in Summer 2013, with its fantastic camera. You would be forgiven for concluding that Microsoft has given up on high-end Windows Phone devices, which is unfortunate for developers since those are the devices likely to deliver more app sales.

If the Lumia brand has become strongly associated with cheap phones it will be hard for the company to convince customers that a high-end device is worth their attention in future.

We may get some phone news soon, linked to the launch of Windows 10; we may hear more at the event on January 21 in New York.

More details here.

# Microsoft Band: do you want to track your health? and with a Microsoft device?

Data on human health has immense value. At an individual level, use of that data has the potential to enhance well-being and productivity, to extend life, and in some cases to avert disaster – such as prompting early investigation into a heart condition. In aggregate, more data on human health enables deeper medical research, especially when combined with other data about lifestyle, profession, location, diet and so on. Medicine is big business, so this is a business opportunity as well as (one hopes) a benefit to humanity.

There is also a dark side to this data. The more data an insurance company has on our health, the more likely they are to exclude the conditions we are most likely to suffer (defeating the purpose of insurance) or to ratchet up premiums for worse risks. Do we trust the industry, whether that is the IT industry or the insurance industry, to safeguard our personal data from being used against us?

The value of this data goes some way to explaining the IT industry’s obsession with fitness gadgets, an obsession that seems to go beyond the demand. I tried a Fitbit for several months, a wristband version. It is a great device, and I found the data interesting, but not enough to motivate me to keep the thing charged up and on my wrist, after the novelty wore off.

The reality is that most of us strike a balance between keeping vaguely fit while not allowing health concerns to dominate our lives. Coffee may be bad for you, but it is also a lovely drink; there is no point in extending life if you cannot also enjoy it.

How much health data, then, is too much?

These questions are likely to come to the fore as increasing numbers of health-monitoring devices come our way, especially multi-purpose devices that do health monitoring as one of several useful functions.

# Microsoft’s glowing Lumia wireless charge pad can show alerts, but we get too many

Today Microsoft/Nokia made a number of announcements alongside the IFA show in Berlin, including a new wireless charging pad for its Lumia phones. Here is the new Lumia 830 while wireless charging.

The new pad glows, with the cool feature being that the phone can send alerts to the pad which cause it to flash. This means that if your phone is charging on a table at home, you can see when there is an alert and pick up the phone to check it out.

What can send an alert? I was told that anything which can appear in the slide-down notification area in Windows Phone 8.1 can also send an alert to the pad, though the user can customise which ones are enabled.

The concept is good, but the difficulty is that we receive so many alerts (most of little real importance) that the pad will be constantly flashing, unless you manage to filter it down things that actually matter; maybe missed calls, voice messages and texts?

# When Windows 8 will not boot: the Automatic Repair disaster

“My PC won’t boot” – never good news, but even worse when there is no backup.

The system was Windows 8. One day, the user restarted his PC and instead of rebooting, it went into Automatic Repair.

Automatic Repair would chug for a bit and then say:

Automatic Repair couldn’t repair your PC. Press “Advanced options” to try other options to repair your PC, or “Shut down” to turn off your PC.

Log file: D:\Windows\System32\Logfiles\Srt\SrtTrail.txt

System Restore can be a lifesaver but in this case had been mysteriously disabled. Advanced start-up options like Safe Mode simply triggered Automatic Repair again.

Choosing Exit and continue to Windows 8.1 triggers a reboot, and you can guess what happens next … Automatic Repair.

You also have options to Refresh or Reset your PC.

Refresh your PC is largely a disaster. It preserves data but zaps applications and other settings. You will have to spend ages updating Windows to get it current, including the update to Windows 8.1 if you originally had Windows 8. You may need to find your installation media if you have any, in cases where there is no recovery partition. You then have the task of trying to get your applications reinstalled, which means finding setup files, convincing vendors that you should be allowed to re-activate and so on. At best it is time-consuming, at worst you will never get all your applications back.

Reset your PC is worse. It aims to restore your PC to factory settings. Your data will be zapped as well as the applications.

You can also reinstall Windows from setup media. Unfortunately Windows can no longer do a repair install, preserving settings, unless you start it from within the operating system you are repairing. If Windows will not boot, that is impossible.

Summary: it is much better to persuade Windows to boot one more time. However if every reboot simply cycles back to Automatic Repair and another failure, it is frustrating. What next?

The answer, it turned out in this case, was to look at the logfile. There was only one problem listed in SrtTrail.txt:

Root cause found:
—————————
Boot critical file d:\windows\system32\drivers\vsock.sys is corrupt.

Repair action: File repair
Result: Failed. Error code =  0×2
Time taken = 12218 ms

I looked up vsock.sys. It is a VMware file, not even part of the operating system. How can this be so critical that Windows refuses to boot?

I deleted vsock.sys using the recovery console. Windows started perfectly, without even an error message, other than rolling back a failed Windows update.

Next, I uninstalled an old vmware player, using control panel. Everything was fine.

### The Automatic Repair problem

If your PC is trapped in the Automatic Repair loop, and you have no working backup, you are in trouble. Why, then, is the wizard so limited? In this case, for example, the “boot critical file” was from a third-party; the wizard just needed to have some logic that says, maybe it is worth trying to boot without it, at least one time.

Finally, if this happens to you, I recommend looking at the logs. It is the only way to get real information about what it going wrong. In some cases you may need to boot into the recovery console from installation media, but if your hard drive is working at all, it should be possible to view those files.