[REQUEST] Win 10 1803 fixes for failed install

Feature updates do not change the partition layout, if you've got three active primary partitions it sounds like you've got an OEM image that's just plain bad. MS isn't responsible for companies like Dell screwing things up! That's why I always install fresh on every build.
This is my third though, all the exact same problem. 2 HP, this is a Lenovo. All within a week.
 
This is my third though, all the exact same problem. 2 HP, this is a Lenovo. All within a week.

What AV? Because Intel and Symantec aren't fully up to speed on 1803 yet. Don't get me started on HP, I refuse to use them anymore for anything. Lenovo I've had good luck with though, but that doesn't mean they're immune from building a defective image.

And failing all of that, consider how many Windows 10 machines there are, how many of them are updating, and you have THREE that died? I personally deal with between 500 and 600 machines in my support umbrella, if only 3 of them fault, that's 0.5% failure... That's statistically insignificant...

Nothing is perfect... ever... I mean what do we want to happen here? Are we complaining about having to do our jobs?
 
Everybody in my area either has Win10 defender, Free AVG, Free Avast, or Free MBAM.

I am selling MBAM premium instead of Kabuto now, and it's actually selling REALLY well.

The old computer repair place I put out of business installed Avast and AVG free versions -.-

Once a month or so I see a Norton or McAfee (thanks Bestbuy and Walmart)
 
Both AVG and Avast are known for blowing feature updates. I've had MBAM on many stations for ages without issue... HOWEVER, the version I did was the old engine. I can say that the new version on this station was active and did just fine.

But the risk of any live scanner running while that upgrade is going is real. This is double true on platter drives, I haven't had a single upgrade issue on Windows 10 on a station that had an SSD. But platter systems? Black screens, stuck on reboots, profile corruption, you name it. Same computer with SSD in it? No more trouble.
 
I've only seen that happen once on Win10, but it's been around for ages. Even XP would sometimes add another boot entry for reasons beyond comprehension. They usually point to the same place, and all work so it's not much of a problem. Other than needing a quick bcdedit to cleanup.
 
4 of these today, one with AVG, 3 with avast. Three with the systemprofile desktop error, empty desktop and unusable taskbar. One with the siihost thing, no desktop or toolbars, just a pointer. Started the 1803 update on all four from task manager, all four cured of all problems. No N/P necessary.
 
4 of these today, one with AVG, 3 with avast. Three with the systemprofile desktop error, empty desktop and unusable taskbar. One with the siihost thing, no desktop or toolbars, just a pointer. Started the 1803 update on all four from task manager, all four cured of all problems. No N/P necessary.

They are finally starting to come in here. Got 3 in and found 1 had AVG and 2 using Avast. All three with the system profile error and siihost thing. I never thought of running the 1803 setup through task manager to fix it though so will try that tomorrow.
 
Lately I have been thinking if a customer only wants free av to just leave them with windows defender & not have to deal with these issues every new build.
 
Precisely, Ctrl-Shift-Esc to open task manager, pop in 1803 disk, New Task, check the run as admin box, browse to setup.exe on your 1803 disc or IODD, run it.
Have the second one in today with this issue and no go on this fix. Neither one would take the update. First one ended up reinstalling the OS completely, and will likely have to on this second. Both had AVG.
 
Back
Top