Windows 10: Did Windows Give UP on the Win 10 Anniversary Update?

hi , Actually you can do this fairly quickly , i ran into a similar issue last week , and following some Help from TopGun here on the Forum, it took 1-2 hours and i had my system up and working again.

have a look at this thread/post

Solved Small Wrinkle in Anniversary Update....MBR Disk - Windows 10 Forums

 

Hi, I came across this thread as I ran into the exact same issue as the OP during the process of installing this anniversary update ("can't access system reserve partition"...blah blah blah...) on my skylake desktop running windows 10 home.

I initially thought the error might be an issue with my SRP being only 100MB (just like the OP); but I decided to hold off on any further attempt at enlarging the SRP and instead tried to install the update on my laptop first.

My laptop has almost the exact same disk partitions as my desktop --- SRP of 100MB, 450MB of Recovery Partition, and rest with the main C: drive. NOW GUESS WHAT? THE UPDATE SUCCEEDED!

So now I'm convinced that my desktop's partition setup is perfectly fine. It has to be something else preventing the update from accessing the SRP.

And to OP -- you're not really missing much as far as new functions go. I really don't see much change from this anniversary update (other than more Cortana integration, perhaps) through normal use the last couple of days on my updated laptop.

 

It seems that Windows Update has woken up and is again trying to install the Anniversary Update, without success. I have been trying to get ready to make the EFI System Partition larger (currently 100MB). I'm going to start another thread to get help with my inability to do a test boot from the Rescue Disk. I'll post here about how it goes.

-- Larry

 

I got brave today and decided to use MiniTool Partition Wizard to change the partitions on my system disk. The ultimate goal was to enlarge the System partition (the first partition) but that meant getting some unallocated space immediately after it.
Here is the original config:



I deleted the HP Recovery partition and then made the 450MB partition larger and moved it to the right to let me move the main C partition to the right giving me room for expanding the system partition. All of that worked.

However, MTPW (and Macrium Reflect) both showed a 128MB partition between the system partition and the main C partition. Windows disk management has never shown that partition. Here are the partitions after I used MTPW to delete the HP Recovery partition and move some things around:




I figured that I would just move the 128MB partition to the right. The issue is that MTPW will not move the 128MB partition so I can not make the system partition larger. MTPW will only delete it or copy it.

No clue what to do next. Suggestions?

-- Larry

 

Minitool Partition Wizard defaults to Enhanced data Protection Mode which is there to prevent any overlap issues (I understand this to prevent alignment issues). this could be the cause of your extra partition it should be one disc sector of unformatted partition (mine are usually as small as 8MB). but can usually be ignored as 128 MB is not anything to worry about loosing with today's Disk sizes,

It can be unchecked if you wish (I normally switch it off as I have full backups of everything so am not worried about it ), and have never had any actual issue

 

System partitions Cant be moved AFAIK ,the 128MB partition is requiredthough that is the windows 8 size I think with win10 it is 16mb. see my Pic below. Unless it is the EFI partition which is now 100mb (99mb)in win10

The Solution is to use Macrium to make an image of C:\ to another Drive eg external. ( or the Windows Partition if not C: )

Boot the Computer to a Win10 AU USB or DVD , Delete ALL partitions (including C:\) on the Disk until it is one big Unallocated Space when asked where you want to install Windows , then hit NEXT and install Win10 AU Clean . Once you have done that you will have the 4 Partitions Win10 uses/needs on the Disk in the Correct Order . Now you can replace the New Windows with the now Existing C:\ you backed Up above.

ie. Boot the Macrium Rescue Disk and use the Image of C:\ you Made to Replace the Newly installed C:\

run the Fix Windows Boot issues while in Macrium to ensure the boot files are good and then boot back into your Old Windows.

there are more details in the link in Post#14 if you need more ? from when I needed to do it.


KB

what you normally see on a GPT disk.....

 

Kbird, The link above leads to a post by you that I'd like a little bit of clarification on. Here's your post:





I'm going for option 1. After doing the fresh OS install, you say to replace the C-drive from the Macrium backup.
Do you mean to replace the C partition with the C partition from the backup? (I'm ignoring the D-drive reference since I don't have one of those.)

I have a Macrium image backup that has all four partitions from my system disk. One partition, the C-partition has all my stuff. Assuming I need to restore just the C-partition, then it's not clear how to do that with Macrium (using the Macrium boot disk of course). The Macrium help info only talks about restoring an entire image. Can you help with that?

Thanks,
Larry

 

Hi Larry , it is fairly simple actually you just drag and drop the C Partition from the backup image onto the newly created C partition ( and resize it if needed) and replace it , you then have your existing Win10 back with all programs and correct partition sizes and hopefully it will update normally after that via Win. Update.

@topgundcp Posted a pic here , but I think he did a video too ..i'll post back if I find it....
https://www.tenforums.com/installatio...tml#post544614

 

Thanks for the clarification, Kbird. I know you didn't write the original version of the 2 options - it's unfortunate that it refers to "drives" rather than "Partitions". I think restoring the entire drive would undo the work previously done.

So, now I'm going to make the leap and do option 1 - it's pretty scary to do a fresh Windows install but I'm sure my backups and the Macrium boot disk will save the day!

I'll report back with results.

-- Larry

 

You are correct if you reimaged the whole drive you would be back at square one....

Test your Macrium Boot disk 1st ......

and make sure to do the Macrium "Fix windows Boot" Option after restoring C Partition....before rebooting ... it's very important....

KB

 

Well, that was exciting! I used the Windows Media Creation Tool (bootable flash drive) to delete all the partitions off my system disk and then install Windows. It installed the *Windows 10 Anniversary Update*. It also set the system disk to have 4 partitions (according to Macrium):
1-Recovery NTFS Primary at 450.0 MB
2-No Name FAT32 Primary at 100.0MB <-- I think this is the EFI System Partition
3-(none) Unformatted Primary at 16.0MB
4- C NTFS Primary at 930.96GB
These partition sizes are no different from what I already had before reinstalling the OS. Hmmmm.....

Using Macrium Boot disk I restored my old C partition to the system disk and fixed boot problems.
This got me a running Win 10 system with all my stuff (sigh of relief) but it's not the Anniversary Update.
Right after booting I got the "Can't install Updates" notification - that is, can't install Anniversary Update.
So, so far there has been no progress but it took a lot of time and worry to get here.

-- Larry

 

NO it won't be the AU update as you imaged back to your old install , but if you had a partition problem on the Disk , the hope was it would fix that and then let Windows Update Run normally and update to AU as it did for me.

If you look at the Disk with Minitool PW is it GPT ?

Sorry been a while and I forget your original error/issue....

 

Kbird, Yes it's a GPT disk.

After my last post I got some upgrade Windows wizard to get the AU installation going. It's been running for about an hour now after it downloaded the files and did some work and then it had me restart.
its 96% done with the first phase of working on the updates. Might get there yet!

I'll report back when it get done.

... Larry

 

The update completed and now I'm running the Anniversary Update! Gads, what a hassle just to get an update to happen. I'm thinking the issue, whatever it was, stemmed from doing an in-place upgrade from Win7 to Win10. Most folks recommended a clean install but I really didn't want to have to reinstall all my apps again. Lucky for me, you folks on this forum told me how to avoid the re-installs.

What do non-technical people do when faced with a problem like this? Call the Geek Squad??

Thanks to all,
-- Larry

 

Great News ! glad it worked out for you too *Smile

KB