Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.

macenied

macrumors 6502a
Original poster
Aug 20, 2014
637
29
This package is a major W10 service release, released today. Tried some system setting changes but no solution up to now from my side. Fails on many systems, not Apple only. Please post solutions when available.

Thank you.
 
Last edited:

flyinmac

macrumors 68040
Sep 2, 2006
3,579
2,464
United States
Don't have any solutions to offer other than to reboot and try to update again. Sometimes that's all it takes.

Installed fine for me today without any issues or hassle on native Mac Pro install, older dell, and newer hp, and a virtual PC.
 

ATC

macrumors 65816
Apr 25, 2008
1,179
427
Canada
FWIW the update installed fine on my early '09 24" iMac but after the first restart, just before going to the log in screen it showed that it was restarting with the spinning beads, which I thought was strange, but after the second restart it wall all good.
 

macenied

macrumors 6502a
Original poster
Aug 20, 2014
637
29
I could not find the W10 issue on my MBP. I ended up with a new and this time really clean installation ( by booting from DVD and formatting the NTFS drive first ) to solve the problem. MacBooks with an optical drive cannot boot Windows from a USB stick.

Background: I updated from W7 Pro to W10 Pro using the option "keep nothing". Thus everyone needs to do an update to get the free W10 license in advance of performing a clean install, I thought I might eventually get away with this and could save some migration efforts.

I have been wrong.

After the clean installation W10 got licensed ( again ) as expected and the major SR update KB3081424 ran without issues. W10 seems to be ok now. Lesson learned: Updating using "keep nothing" and installing clean can be quite a difference. There is no shortcut - you must upgrade first and then perform a clean install, if you want to. I'd recommend a clean install after the initial update.
 
Last edited:

macenied

macrumors 6502a
Original poster
Aug 20, 2014
637
29
And KB3081436 failed as well, this time on my clean W10 install.

Microsoft did not provide a fix but there is a fix on Microsoft answers. This fix works for both updates.

Link:

http://answers.microsoft.com/en-us/...-4377-adf8-04a3beaed7b6?page=~pagenum~&auth=1

Reason:

E. g. the BootCamp 5 Nvidia video driver creates a "zombie user". This user prevents the installation of the service releases. There can be other zombie users as well, depending on how and what you installed. Please read the thread carefully and follow this procedure ( a copy of the most significant posting ) to get rid of the issue:

DETAILED INSTRUCTIONS

BE AWARE THAT IF YOU GET THIS WRONG YOU'LL BE IN ALL SORTS OF TROUBLE!

Be aware that there are almost bound to be some exceptions where these instructions don't work

In the search box type regedit

A the top of the list you should see Regedit and underneath Run Command. Click that and say yes to the User Account Control box if one appears.

Navigate to HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\ProfileList

Double click the key/folder icon to see the contents.

You should see at least 5 keys with the names:

S-1-5-18

S-1-5-19

S-1-5-20

S-1-5-21-(massive long number here)

S-1-5-21-(different massive long number here)

If you don't have at least two entries that begin S-1-5-21- then close the registry editor and look elsewhere for a solution to your problem.

If you have more than one entry beginning S-1-5-21 then open each one in turn at look at the data for the key ProfileImagePath

It should say something like 'C:\Users\fred'

Open File Explorer and navigate to the C:\Users folder (assuming C is the drive letter in the ProfileImagePath data).

You will see several folders there but you should see one called 'fred'

Keep doing this until you find an S-1-5-21-(something) key for which there is no corresponding actual folder .

Before you do anything else, type System Restore into the search box. You should see 'Create a restore point Control panel'. Click that and a System Properties window should open at the System Protection tab. Click create and enter a name in the box (I entered 'manual') then click create. After a while you should get a message 'A restore point has been created successfully'.

Now take the life of your computer in your hands

Go back to Registry editor

Right click the S-1-5-21-(something) key for which there is no corresponding actual folder

(Left) click delete from the drop-down menu

Get this wrong and your computer might not start or one of the user accounts you wanted will be lost.

If it goes wrong, your best hope is to run System Restore and try to go back to the restore point you created.

But if it works there is a good chance the update will now install!
 
Last edited:

flyinmac

macrumors 68040
Sep 2, 2006
3,579
2,464
United States
Interesting. I didn't use boot camp for the drivers. So maybe that's why I didn't have any trouble.

I just installed windows as if my Mac was a PC. Boot camp wasn't involved. Windows 10 had all the drivers built in, and the few that weren't, I got straight from the manufacturer of the part / card.
 

macenied

macrumors 6502a
Original poster
Aug 20, 2014
637
29
Interesting. I didn't use boot camp for the drivers. So maybe that's why I didn't have any trouble.

I just installed windows as if my Mac was a PC. Boot camp wasn't involved. Windows 10 had all the drivers built in, and the few that weren't, I got straight from the manufacturer of the part / card.

According to MS the issues are fixed now - FYI.
 
Register on MacRumors! This sidebar will go away, and you'll see fewer ads.