Hi Paul,Hi @LotharG, are you using old, hidden or recovery partition for that BootCamp?
no, it was a very "normal" bootcamp partition of windows, the only one I ever had. However, I was using Windows through a virtual machine (parallels 13.2) only. When the problem occurred after the windows 1709 update, the win-partition was not even mounted in the Mac system. I could not even press the "activate" key in Macs diskmanager. To dig further into this I used a win10 usb drive to boot the computer (the boot manager recognized the bootable drive..). A blue win10 service screen was shown with options "repair" and "install" windows 10. I tried all the repair options but none of them worked. In the windows command/console window I called the chkdsk (check disk) function. This function reported a major problem in some file allocation table (master boot record kind of thing I suppose) that could not be repaired. At this point I gave up and removed the entire bootcamp partition and I am now using Windows in the VM only (which I did anyway). So, to me it looked like a Windows problem because the windows update appears to have damaged the windows file allocation table.. By the way, I was using the VM when this bad windows update was processed. Eventually I should have done the update in the real bootcamp. But I all the updates before were just working when done in the VM....