Looks like no one’s replied in a while. To start the conversation again, simply ask a new question.

Level 1

0 points

Windows 10 Bootcamp dual boot problem after El Capitan upgrade

Hi guys,

I have an Early 2013 Retina Macbook Pro (2,6 GHz Interl Core i5, (GB DDR3 RAM, 256 GB SSD) computer.

I used OS X Mavericks with Windows 10 Bootcamp and it worked perfectly until I upgraded to OS X El Capitan (I skipped Yosemite).

Now in the boot menu I can see the Windows partition but if I start that I see "Missing operation system" message.

I tried some of the previous discussions:

https://discussions.apple.com/thread/7254934?start=0&tstart=0

https://discussions.apple.com/thread/7200751

http://nerdr.com/bootcamp-partition-lost-repairing-mac-partitions/

but none of them made any result.

I guess I should do some magic with gdisk and the section numbers but I'm not enough by myself to do that, so could you please help me? I can post any result of the gdisk commands to make this work.

Thanks!

Posted on Oct 7, 2015 1:34 PM

63 replies

Loner T

Level 9

59,477 points

Oct 12, 2015 5:19 AM in response to profendre

Safari autocorrected "sfc" to sac. 👿. I meant "sfc".

profendre Author

Level 1

0 points

Oct 12, 2015 5:54 AM in response to Loner T

Here's the log from X:\Windows\Logs\CBS\CBS.log:

2015-10-12 12:15:53, Info CBS TI: --- Initializing Trusted Installer ---

2015-10-12 12:15:53, Info CBS TI: Last boot time: 2015-10-12 07:56:33.499

2015-10-12 12:15:53, Info CBS Starting TrustedInstaller initialization.

2015-10-12 12:15:53, Info CBS Ending TrustedInstaller initialization.

2015-10-12 12:15:53, Info CBS Starting the TrustedInstaller main loop.

2015-10-12 12:15:53, Info CBS TrustedInstaller service starts successfully.

2015-10-12 12:15:53, Info CBS Setup in progress, aborting startup processing checks.

2015-10-12 12:15:53, Info CBS Startup processing thread terminated normally

2015-10-12 12:15:53, Info CBS Starting TiWorker initialization.

2015-10-12 12:15:53, Info CBS Ending TiWorker initialization.

2015-10-12 12:15:53, Info CBS Starting the TiWorker main loop.

2015-10-12 12:15:53, Info CBS TiWorker starts successfully.

2015-10-12 12:15:53, Info CBS TiWorker: Client requests SFP repair object.

2015-10-12 12:15:53, Info CBS Universal Time is: 2015-10-12 20:15:53.568

2015-10-12 12:15:53, Info CBS Loaded Servicing Stack v10.0.10240.16384 with Core: X:\windows\winsxs\amd64_microsoft-windows-servicingstack_31bf3856ad364e35_10.0. 10240.16384_none_115fd2f761f7c508\cbscore.dll

2015-10-12 12:15:53, Info CSI 00000001@2015/10/12:20:15:53.630 WcpInitialize (wcp.dll version 0.0.0.6) called (stack @0x7ffb40468809 @0x7ffb408e91e3 @0x7ffb408acab9 @0x7ff727ac2ee0 @0x7ff727ac3c80 @0x7ffb442fa653)

2015-10-12 12:15:53, Info CBS Scavenge starvation report has never been sent.

2015-10-12 12:15:53, Info CSI 00000002@2015/10/12:20:15:53.693 WcpInitialize (wcp.dll version 0.0.0.6) called (stack @0x7ffb40468809 @0x7ffb401c4fe5 @0x7ffb401c5132 @0x7ff727ac244d @0x7ff727ac3c97 @0x7ffb442fa653)

2015-10-12 12:15:53, Info CSI 00000003 CSI Store 1079057375936 (0x000000fb3cd4e2c0) initialized

2015-10-12 12:15:53, Info CSI 00000004 Transaction merge required, do-not-merge flag passed.

2015-10-12 12:17:56, Info CBS Trusted Installer is shutting down because: SHUTDOWN_REASON_AUTOSTOP

2015-10-12 12:17:56, Info CBS TiWorker signaled for shutdown, going to exit.

2015-10-12 12:17:56, Info CBS Ending the TrustedInstaller main loop.

2015-10-12 12:17:56, Info CBS Starting TrustedInstaller finalization.

2015-10-12 12:17:56, Info CBS Ending TrustedInstaller finalization.

2015-10-12 12:17:56, Info CBS Ending the TiWorker main loop.

2015-10-12 12:17:56, Info CBS Starting TiWorker finalization.

2015-10-12 12:17:56, Info CBS CbsCoreFinalize: ManifestCacheFinalize

2015-10-12 12:17:56, Info CBS CbsCoreFinalize: ExecutionEngineFinalize

2015-10-12 12:17:56, Info CBS CbsCoreFinalize: ComponentAnalyzerFinalize

2015-10-12 12:17:56, Info CBS CbsCoreFinalize: PackageTrackerFinalize

2015-10-12 12:17:56, Info CBS CbsCoreFinalize: CoreResourcesUnload

2015-10-12 12:17:56, Info CBS CbsCoreFinalize: SessionManagerFinalize

2015-10-12 12:17:56, Info CBS CbsCoreFinalize: CapabilityManagerFinalize

2015-10-12 12:17:56, Info CBS CbsCoreFinalize: PublicObjectMonitorFinalize

2015-10-12 12:17:56, Info CBS CbsCoreFinalize: Enter vCoreInitializeLock

2015-10-12 12:17:56, Info CBS CbsCoreFinalize: WcpUnload

2015-10-12 12:17:56, Info CBS CbsCoreFinalize: DrupUnload

2015-10-12 12:17:56, Info CBS CbsCoreFinalize: CfgMgr32Unload

2015-10-12 12:17:56, Info CBS CbsCoreFinalize: DpxUnload

2015-10-12 12:17:56, Info CBS CbsCoreFinalize: SrUnload

2015-10-12 12:17:56, Info CBS CbsCoreFinalize: CbsEsdUnload

2015-10-12 12:17:56, Info CBS CbsCoreFinalize: CbsTraceInfoUninitialize

2015-10-12 12:17:56, Info CBS CbsCoreFinalize: CbsEventUnregister

2015-10-12 12:17:56, Info CBS CbsCoreFinalize: AppContainerUnload

2015-10-12 12:17:56, Info CBS CbsCoreFinalize: WdsUnload, logging from cbscore will end.

2015-10-12 12:17:56, Info CBS Ending TiWorker finalization.

Loner T

Level 9

59,477 points

Oct 12, 2015 7:15 AM in response to profendre

SFC will not find anything on X:, but run the same with C: and see if you get a CBS.log and check for any error messages.

profendre Author

Level 1

0 points

Oct 12, 2015 7:37 AM in response to Loner T

After I googled it, I finally managed to create a relevant CBS log (based on this: http://www.vistax64.com/general-discussion/277903-sfc-runs-finds-errors-but-does -not-create-cbs-log-file.html) .

Here you can find the result: https://dl.dropboxusercontent.com/u/96937737/cbslog.txt

It says that winload exe is corrupted and cannot be recovered... or something like that.

Loner T

Level 9

59,477 points

Oct 12, 2015 8:28 AM in response to profendre

From your log...

grep -i winload cbslog.txt

000022cf [SR] Cannot repair member file [l:22{11}]"winload.exe" of Microsoft-Windows-BootEnvironment-OS-Loader, Version = 10.0.10240.16405, pA = amd64, nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35} in the store, file is missing

000022d0 (F) Failed on regenerating file [l:22{11}]"winload.exe"

000022d1 [SR] Unable to repair \??\C:\WINDOWS\WinSxS\amd64_microsoft-windows-b..vironment-os-loader_31bf3856ad 364e35_10.0.10240.16405_none_6328e45107527462\\[l:22{11}]"winload.exe"

000022d2 [SR] Repaired file \??\C:\WINDOWS\WinSxS\amd64_microsoft-windows-b..vironment-os-loader_31bf3856ad 364e35_10.0.10240.16405_none_6328e45107527462\\[l:22{11}]"winload.exe" by copying from backup

000022d4 [SR] Cannot repair member file [l:22{11}]"winload.exe" of Microsoft-Windows-BootEnvironment-OS-Loader, Version = 10.0.10240.16405, pA = amd64, nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35} in the store, file is missing

000022d6 Hashes for file member \??\C:\WINDOWS\System32\winload.exe do not match actual file [l:22{11}]"winload.exe" :

000022d7 [SR] Could not reproject corrupted file [ml:48{24},l:46{23}]"\??\C:\WINDOWS\System32"\[l:22{11}]"winload.exe"; source file in store is also corrupted

000022dc [SR] Cannot repair member file [l:22{11}]"winload.exe" of Microsoft-Windows-BootEnvironment-OS-Loader, Version = 10.0.10240.16405, pA = amd64, nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35} in the store, file is missing

000022dd (F) Failed on regenerating file [l:22{11}]"winload.exe"

000022de [SR] Unable to repair \??\C:\WINDOWS\WinSxS\amd64_microsoft-windows-b..vironment-os-loader_31bf3856ad 364e35_10.0.10240.16405_none_6328e45107527462\\[l:22{11}]"winload.exe"

000022df [SR] Repaired file \??\C:\WINDOWS\WinSxS\amd64_microsoft-windows-b..vironment-os-loader_31bf3856ad 364e35_10.0.10240.16405_none_6328e45107527462\\[l:22{11}]"winload.exe" by copying from backup

000022e1 [SR] Cannot repair member file [l:22{11}]"winload.exe" of Microsoft-Windows-BootEnvironment-OS-Loader, Version = 10.0.10240.16405, pA = amd64, nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35} in the store, file is missing

000022e3 Hashes for file member \??\C:\WINDOWS\System32\winload.exe do not match actual file [l:22{11}]"winload.exe" :

000022e4 [SR] Could not reproject corrupted file [ml:48{24},l:46{23}]"\??\C:\WINDOWS\System32"\[l:22{11}]"winload.exe"; source file in store is also corrupted

On X: run dir/s/p winload.exe .

profendre Author

Level 1

0 points

Oct 12, 2015 10:16 PM in response to Loner T

Here's the output:

X:\>dir /s /p winload.exe

Volume in drive X is Boot

Volume Serial Number is D60A-0DC2

Directory of X:\Windows\System32

07/10/2015 02:30 AM 1,123,400 winload.exe

1 File(s) 1,123,400 bytes

Directory of X:\Windows\System32\Boot

07/10/2015 02:30 AM 1,123,400 winload.exe

1 File(s) 1,123,400 bytes

Directory of X:\Windows\WinSxS\amd64_microsoft-windows-b..ment-windows-minwin_31bf3856ad364e 35_10.0.10240.16384_none_57ec180996abd934

07/10/2015 02:30 AM 1,123,400 winload.exe

1 File(s) 1,123,400 bytes

Directory of X:\Windows\WinSxS\amd64_microsoft-windows-b..vironment-os-loader_31bf3856ad364e 35_10.0.10240.16384_none_63272be107542aec

07/10/2015 02:30 AM 1,123,400 winload.exe

1 File(s) 1,123,400 bytes

Total Files Listed:

4 File(s) 4,493,600 bytes

0 Dir(s) 534,630,400 bytes free

X:\>

Loner T

Level 9

59,477 points

Oct 13, 2015 4:54 AM in response to profendre

Do the same on C: and if possible copy the C: winload.exe with a different filename. We need to verify the the integrity and replace the one on C: with the one on X:.

profendre Author

Level 1

0 points

Oct 13, 2015 5:02 AM in response to Loner T

Thanks for your reply. Here's the output of c:\>dir /s /p winload.exe:

C:\>dir /s /p winload.exe

Volume in drive C is BOOTCAMP

Volume Serial Number is 983B-4960

Directory of C:\Windows\System32

07/10/2015 02:30 AM 1,123,400 winload.exe

1 File(s) 1,123,400 bytes

Directory of C:\Windows\System32\Boot

07/25/2015 09:14 PM 1,123,400 winload.exe

1 File(s) 1,123,400 bytes

Directory of C:\Windows\WinSxS\amd64_microsoft-windows-b..ment-windows-minwin_31bf3856ad364e 35_10.0.10240.16384_none_57ec180996abd934

08/13/2015 08:27 AM 58,734 winload.exe

1 File(s) 58,734 bytes

Directory of C:\Windows\WinSxS\amd64_microsoft-windows-b..ment-windows-minwin_31bf3856ad364e 35_10.0.10240.16405_none_57edd07996aa22aa

07/25/2015 09:14 PM 1,123,400 winload.exe

1 File(s) 1,123,400 bytes

Directory of C:\Windows\WinSxS\amd64_microsoft-windows-b..vironment-os-loader_31bf3856ad364e 35_10.0.10240.16384_none_63272be107542aec

08/13/2015 08:27 AM 58,734 winload.exe

1 File(s) 58,734 bytes

Total Files Listed:

5 File(s) 3,487,668 bytes

0 Dir(s) 71,717,666,816 bytes free

Now, what should I do with this files and after that?

Loner T

Level 9

59,477 points

Oct 13, 2015 5:12 AM in response to profendre

Copy the file in system32\boot to your X: with a different name. Switch to OS X. We need to run a check similar to the following.

find . -name winload.exe -print -exec openssl md5 {} \;

./Windows/System32/Boot/winload.exe

MD5(./Windows/System32/Boot/winload.exe)= 8d4eca2cc4cc79a32a7e74bbda612eaa

./Windows/System32/winload.exe

MD5(./Windows/System32/winload.exe)= 8d4eca2cc4cc79a32a7e74bbda612eaa

./Windows/WinSxS/amd64_microsoft-windows-b..ment-windows-minwin_31bf3856ad364e35 _6.3.9600.16384_none_40aa0665cff59504/winload.exe

MD5(./Windows/WinSxS/amd64_microsoft-windows-b..ment-windows-minwin_31bf3856ad36 4e35_6.3.9600.16384_none_40aa0665cff59504/winload.exe)= 8d4eca2cc4cc79a32a7e74bbda612eaa

./Windows/WinSxS/amd64_microsoft-windows-b..vironment-os-loader_31bf3856ad364e35 _6.3.9600.16384_none_4be51a3d409de6bc/winload.exe

MD5(./Windows/WinSxS/amd64_microsoft-windows-b..vironment-os-loader_31bf3856ad36 4e35_6.3.9600.16384_none_4be51a3d409de6bc/winload.exe)= 8d4eca2cc4cc79a32a7e74bbda612eaa

Notice in my case, the MD5sums are identical, but in your case they should be different. This is verification before we replace files.

profendre Author

Level 1

0 points

Oct 13, 2015 5:41 AM in response to Loner T

OK. So, I copied my C:\Windows\System32\Boot folder to my usb drive (D:) and also to the temporal boot drive (X:).

Then I switched to OS X, listed the Bootcamp volume (cd /Volumes/Bootcamp), then I ran your command:

find . -name winload.exe -print -exec openssl md5 {} \;

./Windows/System32/Boot/winload.exe

MD5(./Windows/System32/Boot/winload.exe)= 6e8b85a2274d2a7898ad88c844e87ef4

./Windows/System32/winload.exe

MD5(./Windows/System32/winload.exe)= 4eb82e956568f23e8b04f4f05a60dd83

./Windows/WinSxS/amd64_microsoft-windows-b..ment-windows-minwin_31bf3856ad364e35 _10.0.10240.16384_none_57ec180996abd934/winload.exe

MD5(./Windows/WinSxS/amd64_microsoft-windows-b..ment-windows-minwin_31bf3856ad36 4e35_10.0.10240.16384_none_57ec180996abd934/winload.exe)= 0ba0c50d2e6ec5658713b453389659b9

./Windows/WinSxS/amd64_microsoft-windows-b..ment-windows-minwin_31bf3856ad364e35 _10.0.10240.16405_none_57edd07996aa22aa/winload.exe

MD5(./Windows/WinSxS/amd64_microsoft-windows-b..ment-windows-minwin_31bf3856ad36 4e35_10.0.10240.16405_none_57edd07996aa22aa/winload.exe)= 6e8b85a2274d2a7898ad88c844e87ef4

./Windows/WinSxS/amd64_microsoft-windows-b..vironment-os-loader_31bf3856ad364e35 _10.0.10240.16384_none_63272be107542aec/winload.exe

MD5(./Windows/WinSxS/amd64_microsoft-windows-b..vironment-os-loader_31bf3856ad36 4e35_10.0.10240.16384_none_63272be107542aec/winload.exe)= 0ba0c50d2e6ec5658713b453389659b9

Then I switched to my backup folder on my Windows Installer USB drive and also ran the command:

Endres-Macbook-Pro:backup endredeak$ find . -name winload.exe -print -exec openssl md5 {} \;

./winload.exe

MD5(./winload.exe)= 7eaf2f0acfee4c463f69bfb7f96c0446

This is different to the others....

Loner T

Level 9

59,477 points

Oct 13, 2015 6:31 AM in response to profendre

profendre wrote:

Directory of C:\Windows\WinSxS\amd64_microsoft-windows-b..ment-windows-minwin_31bf3856ad364e 35_10.0.10240.16405_none_57edd07996aa22aa

07/25/2015 09:14 PM 1,123,400 winload.exe

1 File(s) 1,123,400 bytes

Can you copy this file to c:\windows\system32 and c:\windows\system32\boot and test?

profendre Author

Level 1

0 points

Oct 13, 2015 6:42 AM in response to Loner T

I copied to both folders, tried to reboot but nothing changed.

Loner T

Level 9

59,477 points

Oct 13, 2015 7:53 AM in response to profendre

Can you verify the the md5sums match in your source and destination folders? Windows Startup may replace files.

profendre Author

Level 1

0 points

Oct 13, 2015 8:25 AM in response to Loner T

MD5(./Windows/System32/Boot/winload.exe)= 6e8b85a2274d2a7898ad88c844e87ef4

MD5(./Windows/System32/winload.exe)= 7eaf2f0acfee4c463f69bfb7f96c0446

MD5(./Windows/WinSxS/amd64_microsoft-windows-b..ment-windows-minwin_31bf3856ad36 4e35_10.0.10240.16384_none_57ec180996abd934/winload.exe)= 0ba0c50d2e6ec5658713b453389659b9

MD5(./Windows/WinSxS/amd64_microsoft-windows-b..ment-windows-minwin_31bf3856ad36 4e35_10.0.10240.16405_none_57edd07996aa22aa/winload.exe)= 6e8b85a2274d2a7898ad88c844e87ef4

MD5(./Windows/WinSxS/amd64_microsoft-windows-b..vironment-os-loader_31bf3856ad36 4e35_10.0.10240.16384_none_63272be107542aec/winload.exe)= 0ba0c50d2e6ec5658713b453389659b9

and the backup:

MD5(./backup/winload.exe)= 7eaf2f0acfee4c463f69bfb7f96c0446

As I can see System32/winload.exe and System32/Boot/winload.exe is different.

Should I overwrite them again and hope ?

Loner T

Level 9

59,477 points

Oct 13, 2015 8:38 AM in response to profendre

Please overwrite and verify on C:. Make sure you have read-write access to C: using Diskpart before you modify. Check for any copy errors.

Windows 10 Bootcamp dual boot problem after El Capitan upgrade