Windows 10 can't tell if I have enough space on my PC. I have over 350gb free.

Question

Level 1

1 points

Windows 10 can't tell if I have enough space on my PC. I have over 350gb free.

Now that Boot Camp 6 is out I wanted to update my Boot Camp partition from Windows 8.1 to Windows 10. I keep getting the following error when I do. "Something Happened. We can't tell if your PC has enough space to continue." That is when I try to do it with an .iso. When I try through windows update it gives me the following error code: 8007001F. I have included the following data in hopes it will help with a solution. I have seen that some people mention there is a posible partitioning error that may be causing this but not really a solution yet on how to fix it. I have over 350gb free so that should not be the issue. My computer does have a SSD drive if that is something to consider. Thank you for your time and help with this. I am really hoping I do not have to do a fresh install of Windows 10 and can just continue to do an upgrade of my current Windows 8.1 partition.

/dev/disk0

#: TYPE NAME SIZE IDENTIFIER

0: GUID_partition_scheme *1.0 TB disk0

1: EFI EFI 209.7 MB disk0s1

2: Apple_HFS Macintosh HD 251.0 GB disk0s2

3: Apple_Boot Recovery HD 650.0 MB disk0s3

4: Microsoft Basic Data BOOTCAMP 748.7 GB disk0s4

No CoreStorage logical volume groups found

gpt show: /dev/disk0: mediasize=1000555581440; sectorsize=512; blocks=1954210120

gpt show: /dev/disk0: PMBR at sector 0

gpt show: /dev/disk0: Pri GPT at sector 1

gpt show: /dev/disk0: Sec GPT at sector 1954210119

start size index contents

0 1 PMBR

1 1 Pri GPT header

2 32 Pri GPT table

34 6

40 409600 1 GPT part - C12A7328-F81F-11D2-BA4B-00A0C93EC93B

409640 490234368 2 GPT part - 48465300-0000-11AA-AA11-00306543ECAC

490644008 1269536 3 GPT part - 426F6F74-0000-11AA-AA11-00306543ECAC

491913544 1720

491915264 1462294528 4 GPT part - EBD0A0A2-B9E5-4433-87C0-68B6B72699C7

1954209792 295

1954210087 32 Sec GPT table

1954210119 1 Sec GPT header

Disk: /dev/disk0 geometry: 121643/255/63 [1954210120 sectors]

Signature: 0xAA55

Starting Ending

#: id cyl hd sec - cyl hd sec [ start - size]

------------------------------------------------------------------------

1: EE 1023 254 63 - 1023 254 63 [ 1 - 1954210119] <Unknown ID>

2: 00 0 0 0 - 0 0 0 [ 0 - 0] unused

3: 00 0 0 0 - 0 0 0 [ 0 - 0] unused

4: 00 0 0 0 - 0 0 0 [ 0 - 0] unused No

Re: Windows 10 upgrade error with Boot Camp on Macbook Pro

MacBook Pro (Retina, 15-inch, Mid 2014), OS X Yosemite (10.10.5), Windows 10

Posted on Aug 15, 2015 9:16 AM

Reply

Answer 1

Nov 14, 2017 9:58 PM in response to Loner T

I just wanted to say that this also fixed my problem upgrading to Fall Creators Upgrade on my Macbook Pro, so thumbsup :-)

Reply

Answer 2

Loner T

Level 9

59,536 points

Nov 15, 2017 3:21 AM in response to WindowsIsCool

😎. Please remember regular backups will help prevent future frustration.

Reply

Answer 3

mende1

Level 10

93,624 points

Aug 15, 2015 9:22 AM in response to eibrahim69

First of all, have you installed Boot Camp 6 drivers on Windows? If not, open Apple Software Update and install them. It is highly recommended to install them before upgrading Windows.

Then, try upgrading through the Windows 10 Media Creation Tool by choosing the "Upgrade this PC now" option. This option will download Windows 10 onto your Mac again to make sure that the ISO file was not corrupted, and follow the steps to upgrade.

Another thing you should try is to unmount the OS X partition in Windows, to make sure that the Windows 10 installer does not get confused with a different partition.

Reply

Answer 4

eibrahim69 Author

Level 1

1 points

Aug 15, 2015 4:00 PM in response to mende1

I have made sure that all of my apple drivers are updated and from what I understand you can't get the bootcamp 6 drivers until you are actually able to install Windows 10. Is there another way to get them?

I have tried to us the Windows 10 media tool and when I have used that option it gave me the Something Happened error about not being able to tell if the PC has enough space.

I have not tried the unmounting of the Mac drive you mentioned though. Do you have a link or can you explain how that may be done in windows? Thanks for your time and help.

Reply

Answer 5

eibrahim69 Author

Level 1

1 points

Aug 17, 2015 11:44 AM in response to eibrahim69

I am including my setupact.log just in case it might help:

[12255]=[0x0]

2015-08-17 10:59:42, Error MOUPG MoSetupPlatform: SetupPlatform::SetSqmDatapoint(DWORD) returned: [0x80004005]

2015-08-17 10:59:42, Info MOUPG CSetupDiagnostics: Tracing Data [DWORD] -> [CompatInstallReqTime]=[0x52] [21e5fe04-9aaa-4cb9-b6fe-b9ea9f07de58][{ACDF403A-21F4-4B3F-A72D-E1A28266D6AF}.2 00][][0x5]

2015-08-17 10:59:42, Info MOUPG CSetupDiagnostics: Tracing Data [STRING] -> [HostOsEditionId]=[Professional] [21e5fe04-9aaa-4cb9-b6fe-b9ea9f07de58][{ACDF403A-21F4-4B3F-A72D-E1A28266D6AF}.2 00][][0x5]

2015-08-17 10:59:42, Info MOUPG CSetupDiagnostics: Tracing Data [STRING] -> [HostOsInstallationType]=[Client] [21e5fe04-9aaa-4cb9-b6fe-b9ea9f07de58][{ACDF403A-21F4-4B3F-A72D-E1A28266D6AF}.2 00][][0x5]

2015-08-17 10:59:42, Info MOUPG CSetupDiagnostics: Tracing Data [STRING] -> [HostOsSkuName]=[Windows 8.1 Pro] [21e5fe04-9aaa-4cb9-b6fe-b9ea9f07de58][{ACDF403A-21F4-4B3F-A72D-E1A28266D6AF}.2 00][][0x5]

2015-08-17 10:59:42, Info MOUPG CSetupDiagnostics: Tracing Data [STRING] -> [HostOsBranchName]=[winblue_r4] [21e5fe04-9aaa-4cb9-b6fe-b9ea9f07de58][{ACDF403A-21F4-4B3F-A72D-E1A28266D6AF}.2 00][][0x5]

2015-08-17 10:59:42, Info CONX ConX::Compatibility::CCompatibilityHost::SetCorrelationVector:(wsc:setup:): Correlation Vector [IT7EyReZQ0S0rYTU.9.7.0]

2015-08-17 10:59:42, Info CONX ConX::Compatibility::CCompatibilityHost::SetCorrelationVector:(wsc:wica:): Correlation Vector [IT7EyReZQ0S0rYTU.9.8.0]

2015-08-17 10:59:42, Info CONX Compatibility Finalize called

2015-08-17 10:59:42, Info MOUPG Finalize: Requesting ASIMOV upload.

2015-08-17 10:59:42, Info MOUPG Finalize: Remapping install error [0x8007001F] -> [0xC1900108] for telemetry.

2015-08-17 10:59:42, Info MOUPG Finalize: Reporting result value: [0xC1900108]

2015-08-17 10:59:42, Info MOUPG MoSetupPlatform: Reporting SQM [DWORD] -> [12501]=[0xc1900108]

2015-08-17 10:59:42, Error MOUPG MoSetupPlatform: SetupPlatform::SetSqmDatapoint(DWORD) returned: [0x80004005]

2015-08-17 10:59:42, Info MOUPG CSetupDiagnostics: Tracing Data [DWORD] -> [Setup360MappedResult]=[0xC1900108] [21e5fe04-9aaa-4cb9-b6fe-b9ea9f07de58][{ACDF403A-21F4-4B3F-A72D-E1A28266D6AF}.2 00][][0x5]

2015-08-17 10:59:42, Info MOUPG CSetupDiagnostics: Tracing Data [DWORD] -> [Setup360Result]=[0x8007001F] [21e5fe04-9aaa-4cb9-b6fe-b9ea9f07de58][{ACDF403A-21F4-4B3F-A72D-E1A28266D6AF}.2 00][][0x5]

2015-08-17 10:59:42, Info MOUPG CSetupDiagnostics: Tracing Data [DWORD] -> [Setup360Extended]=[0x4001C] [21e5fe04-9aaa-4cb9-b6fe-b9ea9f07de58][{ACDF403A-21F4-4B3F-A72D-E1A28266D6AF}.2 00][][0x5]

2015-08-17 10:59:42, Info MOUPG CSetupDiagnostics: Tracing Data [CUSTOM] -> [WindowsUpdateExit] -> [fecb5ef6-453e-4e45-ba67-b8f48cadb3f5] [21e5fe04-9aaa-4cb9-b6fe-b9ea9f07de58][{ACDF403A-21F4-4B3F-A72D-E1A28266D6AF}.2 00][][0x5]

2015-08-17 10:59:42, Info MOUPG Finalize: Retrieving downlevel ticks from registry...

2015-08-17 10:59:42, Info MOUPG Finalize: Converting [33] downlevel ticks to seconds...

2015-08-17 10:59:42, Info MOUPG Finalize: Reporting total downlevel time: [165 seconds]

2015-08-17 10:59:42, Info MOUPG MoSetupPlatform: Reporting SQM [DWORD] -> [12500]=[0xa5]

2015-08-17 10:59:42, Error MOUPG MoSetupPlatform: SetupPlatform::SetSqmDatapoint(DWORD) returned: [0x80004005]

2015-08-17 10:59:42, Info MOUPG CSetupDiagnostics: Tracing Data [DWORD] -> [Setup360DownlevelTime]=[0xA5] [21e5fe04-9aaa-4cb9-b6fe-b9ea9f07de58][{ACDF403A-21F4-4B3F-A72D-E1A28266D6AF}.2 00][][0x5]

2015-08-17 10:59:42, Info MOUPG MoSetupPlatform: Releasing Setup Platform object...

2015-08-17 10:59:42, Info SP Releasing the setup platform

2015-08-17 10:59:42, Info SP StopTelemetry: 1, UploadTelemetryData: 0, CV:IT7EyReZQ0S0rYTU.13

2015-08-17 10:59:42, Info SP Try to merge diagnostics data from default new system data file

2015-08-17 10:59:42, Info Initializing diagnostics helper; data file = C:\$WINDOWS.~BT\Sources\Diagnostics\diagnostics.dat

2015-08-17 10:59:42, Info Found existing diagnostics data, attempting to load it.

2015-08-17 10:59:42, Info Default SQM Session ID: 142848

2015-08-17 10:59:42, Info Extra SQM Session ID: 101458003

2015-08-17 10:59:42, Warning Merging diagnostics data fails since not opted-in

2015-08-17 10:59:42, Info SP Finish merge diagnostics data

2015-08-17 10:59:42, Info SP Start uploading diagnostics data for setup platform

2015-08-17 10:59:42, Info SP Not opted-in to SQM. Diagnostics data will NOT be uploaded

2015-08-17 10:59:42, Info Key CollectTrace is not available.

2015-08-17 10:59:43, Info SP Upload telemetry data based on environment variable

2015-08-17 10:59:44, Info Copy telemetry file: source folder: C:\$WINDOWS.~BT\Sources\Panther, destination folder: C:\ProgramData\Microsoft\Diagnosis\ETLLogs

2015-08-17 10:59:44, Info Copy etl files: source: C:\$WINDOWS.~BT\Sources\Panther\DlTel-Merge.etl, destination: C:\ProgramData\Microsoft\Diagnosis\ETLLogs\DlTel-Merge.etl

2015-08-17 10:59:44, Info Copy etl files: source: C:\$WINDOWS.~BT\Sources\Panther\DlTel-Merge1.etl, destination: C:\ProgramData\Microsoft\Diagnosis\ETLLogs\DlTel-Merge1.etl

2015-08-17 10:59:44, Info Diagtrack service is running

2015-08-17 10:59:44, Info Restart Diagtrack service successfully

2015-08-17 10:59:44, Info SP Closing Panther Logging

2015-08-17 10:59:44, Info MOUPG MoSetupPlatform: Setup Platform object released!

2015-08-17 10:59:45, Info MOUPG Finalize: Leaving Execute Method

2015-08-17 10:59:45, Warning MOUPG CSetupDiagnostics::ReportData - Not reporting WINDLP data point [0x2004]

2015-08-17 10:59:45, Warning MOUPG CSetupDiagnostics::ReportData - Not reporting WINDLP data point [0x2003]

2015-08-17 10:59:45, Warning MOUPG CSetupDiagnostics::ReportData - Not reporting WINDLP data point [0x2001]

2015-08-17 10:59:45, Info MOUPG ProgressHandlerAction: Sending final progress message for action [0].

2015-08-17 10:59:45, Info MOUPG ProgressHandlerAction FinalUpdate: 0x0, 0x0 / 0x0, 0x0

2015-08-17 10:59:45, Info MOUPG ProgressHandlerAction: Sending final progress message for action [0].

2015-08-17 10:59:45, Info MOUPG ProgressHandlerAction FinalUpdate: 0x0, 0x0 / 0x0, 0x0

2015-08-17 10:59:45, Info MOUPG ProgressHandlerAction: Sending final progress message for action [0].

2015-08-17 10:59:45, Info MOUPG ProgressHandlerAction FinalUpdate: 0x0, 0x0 / 0x0, 0x0

2015-08-17 10:59:45, Info MOUPG Waiting for actions thread to exit.

2015-08-17 10:59:45, Info MOUPG Actions thread has exited.

2015-08-17 10:59:45, Warning MOUPG CSetupDiagnostics::ReportData - Not reporting WINDLP data point [0x2004]

2015-08-17 10:59:45, Warning MOUPG CSetupDiagnostics::ReportData - Not reporting WINDLP data point [0x2000]

2015-08-17 10:59:46, Warning MOUPG CSetupDiagnostics::ReportData - Not reporting WINDLP data point [0x3000]

2015-08-17 10:59:46, Info MOUPG DlpTask: Leaving Execute Method

2015-08-17 10:59:46, Info MOUPG SetupNotify: Specifying extended data [0x4001C] for error [0x8007001F].

2015-08-17 10:59:46, Info MOUPG SetupHost: Reporting error event -> [0x8007001F, 0x4001C]

2015-08-17 10:59:46, Info MOUPG SetupNotify::ReportEvent - ReportSetupEvent [{ACDF403A-21F4-4B3F-A72D-E1A28266D6AF}.200,0x2,0x8007001F,0x4001C,0x1]

2015-08-17 10:59:46, Error MOUPG CSetupHost::ReportEventW(1618): Result = 0x8024F005[gle=0x000003f0]

2015-08-17 10:59:46, Error MOUPG SetupHost: Reporting failure event failed: hr = [0x8024F005]

2015-08-17 10:59:46, Info MOUPG SetupManager: FailureCount = [18]

2015-08-17 10:59:46, Info MOUPG SetupManager: Requesting cleanup level [0x2] from parent process.

2015-08-17 10:59:46, Info MOUPG Setup phase change: [SetupPhaseError] -> [SetupPhaseUnpack]

2015-08-17 10:59:47, Info MOUPG SetupManager: Deleting task: [PreDownload]...

2015-08-17 10:59:47, Info MOUPG SetupManager: Deleting task: [Prepare]...

2015-08-17 10:59:48, Info MOUPG SetupManager: Deleting task: [Exit]...

2015-08-17 10:59:48, Info MOUPG SetupManager: Found unpack task! Restarting layout action...

2015-08-17 10:59:48, Error MOUPG CSetupManager::Execute(223): Result = 0x8007001F

2015-08-17 10:59:48, Error MOUPG CSetupHost::Execute(370): Result = 0x8007001F

2015-08-17 10:59:48, Info CONX Uninitializing compatibility provider wsc:setup:...

2015-08-17 10:59:48, Info CONX Uninitializing compatibility provider wsc:wica:...

2015-08-17 10:59:48, Info MOUPG SetupUI: Calling PowerClearRequest with type [0x1]...

2015-08-17 10:59:48, Info MOUPG SetupUI: Power request cleared!

Reply

Answer 6

Sep 30, 2015 12:52 AM in response to eibrahim69

Not sure if you have been able to solve your problem in the meantime, but for future reference I decided to post my solution anyway.

I had the same "Something Happened. We can't tell if your PC has enough space to continue installing Windows 10" error like you did, when upgrading my Windows 8.1 bootcamp installation to Windows 10 on my 2014 Macbook Pro with SSD. Finally, this is what solved it:

1. Make Windows you default startup disk. Go to System Preferences -> Startup Disk -> Select you windows installation -> Restart... What this does, is setting Windows as you primary OS. So if you start you Mac and you don't press the option key, it will boot in Windows. When the Windows 10 upgrade is complete you can set this back to OS X.

2. Unplug all devices (usb-drives, keyboards, external harddrives, thunderbolt cables, etc.) you don't need. I ended up only having my power cable connected.

3. In Windows, download the Windows 10 media creation tool for your system (32-bit or 64-bit) and launch it. Select "Upgrade this PC" to download Windows 10 and start the installation.

4. When the installation is finished, run "Apple Software Update" in Windows 10, and install the Bootcamp 6 update for Windows 10.

Hopefully this solution works for you as well!

Reply

Answer 7

Nov 15, 2015 5:13 AM in response to PascAlcatraz

I'm also hitting this problem when I try to update my working Windows 10 Boot Camp installation with the Windows 10 November Update.

- I have the Boot Camp 6 drivers installed.

- In Mac OS, I set the Startup Disk to the Windows partition.

- I have nothing connected to my MacBook Pro.

- I run the Windows 10 Media Creation Tool, and let it download the update.

- Just before the Media Creation Tool is about to begin the update, it stops with the message:

Something happened

We can't tell if your PC has enough space to continue installing Windows 10.

I'm not able to find any way around this problem.

Reply

Answer 8

Loner T

Level 9

59,536 points

Nov 15, 2015 9:23 AM in response to Brian Kendig

Should you not be doing an in-place upgrade when booted in Windows?

Reply

Answer 9

Nov 15, 2015 12:09 PM in response to Loner T

I am booted into Windows when I'm trying this.

When I try to install the update via Windows Update, it fails with error 0x8007001F.

When I try to use the Media Creation Tool, it says "We can't tell if your PC has enough space to continue installing Windows 10."

Reply

Answer 10

Loner T

Level 9

59,536 points

Nov 15, 2015 1:37 PM in response to Brian Kendig

Can you download the ISO to your Windows Desktop and run setup.exe once it is mounted?

Reply

Answer 11

Nov 15, 2015 4:39 PM in response to Loner T

Good thought, but same "can't tell if your PC has enough space" error. Also, same error if I use the Media Creation Tool to put the installer on a USB drive and run it from there.

Reply

Answer 12

Loner T

Level 9

59,536 points

Nov 15, 2015 4:52 PM in response to Brian Kendig

Before you start the upgrade, can you run chkdsk?

Reply

Answer 13

Nov 15, 2015 4:56 PM in response to Loner T

chkdsk reports no problems, nor does sfc /scannow or dism /online /cleaup-image /checkhealth.

I'm open to trying anything you can think of - I'm stumped! Some forums say that this error indicates a problem with the MBR, but this is a UEFI installation of Windows 10.

Reply

Answer 14

Loner T

Level 9

59,536 points

Nov 15, 2015 5:13 PM in response to Brian Kendig

Macs prior to 2012 do not support W10. Models that support W10 do it using EFI. The EFI can reside in the Mac's EFI, or can work in conjunction with an MSR.

To confirm, you can check msinfo32.

Can you try the following two procedures and test?

Resetting the System Management Controller (SMC) on your Mac - Apple Support

How to Reset NVRAM on your Mac - Apple Support

Reply

Answer 15

Nov 15, 2015 5:18 PM in response to Loner T

This is a MacBook Pro (Retina, 15-inch, Late 2013) that's already running Windows 10 (Build 10240) in UEFI mode.

Good thought to reset SMC and NVRAM; lemme give that a try...

Reply