Windows – Partition file system changed to “RAW” after Windows 10 update

Faced that issue today, my way to solve it:

1. Start up with F8
2. Run in safe mode
3. Windows should uninstall dubious KB2160329
4. Make sure that you will restart back to safe mode
5. Restart to normal mode
6. Windows will revert the update here as well

Hope that helps..

By the way, I've spotted that in C:\Windows\System32 I have now the 6.1.7600.16585 version, while the latest available in the system is 6.1.7600.20738 (check C:\Windows\winsxs). Might it be some case of signature overwriting?

I'm pretty sure you've created a highly dangerous and inconsistent layout.

The problem is this: Macs that dual-boot with Windows generally use a hybrid MBR, which is a way to get two partition tables to (sort-of) coexist on a disk. The GUID Partition Table (GPT) is the authoritative partition table and is the one that MUST be modified by any tool that resizes partitions. In a hybrid MBR setup, one or more normally-empty fields in the Master Boot Record (MBR) are employed to replicate data in the GPT data structures. When confronted with a hybrid MBR disk, OS X uses the GPT data, whereas Windows uses the MBR data. A hybrid MBR is also used as a signal to the Mac's firmware that the disk may be booted in BIOS mode (vs. the EFI mode that OS X uses).

The trouble with this is that if you use a GPT-unaware tool to resize, move, or create partitions, you'll be changing the unauthoritative MBR data structures while not changing the authoritative GPT data structures. That's sort of like entering a deposit in your checkbook without actually depositing a check -- it may look cool to have $1,000,000 in your bank account, but if you try to use the money, you'll be in trouble! This is (I think) what you've done -- by changing the MBR data structures, you've created a partition that Windows can use but that OS X can't. Worse, depending on the details of what you've done, you may be damaging one OS's files whenever you write information in the other OS.

To recover, I recommend that you first back up everything to another disk.

With that done, you can attempt a data recovery by examining the start and end points of both the GPT and MBR data. You can do this with gdisk -- an ordinary p command displays the GPT data; and in the experts' menu or the recovery menu, an o command displays the MBR data. (Ignore the type-0xEE MBR partition; that signals that the disk is a GPT disk, nothing more.) Figure out which partitions match and which don't. Make note of which partition(s) you use from OS X, and which you use from Windows. The Windows partitions will be on the MBR side. Once you've figured out which partitions you're using, delete the non-functional GPT partitions and, in their place, create new partitions with the same start and end points as the MBR partitions that work in Windows. This procedure assumes that you can actually create these partitions; if they overlap, you're in deep trouble and you'll really have to delete all the overlapping partitions, create new ones, and restore everything from your backups. Once you've done all this, you can create a new hybrid MBR, as described on my Web page.

In the future, be sure to obey Rule #1 for hybrid MBRs:

NEVER, EVER USE GPT-UNAWARE UTILITIES ON A HYBRID MBR DISK!

In some cases, you'll need to modify the GPT data structures with a GPT-only tool and then create a new hybrid MBR to reflect the changes.