Windows 10: Windows 10 version 1903 problem with user profile: Microsoft's Response

I have been having problems with the update to Version 1903 of Windows 10.


Besides taking about 12 hours to download and update, I discovered that my user profile had been moved to an 'old' profile called [username].000


I rolled back and tried again, with the same result. I went direct to the Microsoft site and downloaded the Update Assistant and tried again, with the same result.


I followed a tip from the Microsoft Community about restarting 3-4 times, but nothing changed.


I have just now had a Microsoft technician (Nikhail) controlling my machine, and he says it's the BIOS on my PC that is out of date - despite the Windows Update checking my machine and stating it was able to receive the update.


Nikhail (representing Microsoft) told me that I should "upgrade my PC rather than waste more of Microsoft's time".


And there we have it - a total lack of care and concern, and exceptionally poor customer service. I will, of course, be making a formal complaint, because it's in my nature.

:)

 

Local profile issue after upgrading to 1903


Hi roblinb

Not listed in the Known.

Known issues for Windows 10 May 2019 Update version 1903


As far as Wifi any chance it is Qualcom inside USB adapter, if Qualcom then yes known issue.


I might create another user (Local) and when if try again see if this issue occurs on both users.

Would also suggest you run the first 5 steps in this tutorial to see if you have any corruption with current build.

Use DISM to Repair Windows 10 Image


Ken

 

(WINDOWS 10)"The User Profile Service failed the logon. User profile cannot be loaded."

Hi Ashley,

Thank you for posting your query in Microsoft Community. We appreciate your interest in Windows 10.

I understand the inconvenience caused to you while logging-in with the guest user account on Windows 10.

This issue might be due to the User profile Services, please follow the below and check.

I suggest you to Check the status of User profile services.

Steps:

• Press Windows + R to open Run command, type
  Services.msc and press Enter.
• Search for User Profile Service, right click on it and
  start the service.
• Also, set the Startup type to
  Automatic.
• Now check if you are able to log-in.

Hope it helps. Kindly update the status of this issue, we will be happy to assist you further.

 

Microsoft Botches Up UEFI Support for Windows 7 on ASUS Motherboards



Microsoft suggests updating to Windows 10 to patch Windows 7

• 
  
  
• Chris Merriman
• 
  @ChrisTheDJ
• 05 May 2016

• Tweet
• Facebook
• Google plus
• Send to

9 Comments

MICROSOFT HAS confirmed a potentially lappy-borking problem that it won't be fixing, because Windows 7.

Woody Leonhard, the respected Windows columnist, points to a problem involving Asus motherboards, which also appear rebadged in a variety of other manufacturers' machines, and the activation of UEFI Secure Boot for Windows 7 in a patch KB3133977.

Short version: install update, welcome to Borksville, population you.

Both Asus and Microsoft acknowledged the problem. Microsoft entitled the article "BitLocker can't encrypt drives because of service crashes in svchost.exe process in Windows 7 or Windows Server 2008 R2", but we prefer to just call it "Trevor for brevity."

The firm's advice was that it's an optional update, leave well alone, you'll be fine, or alternatively turn secure boot off.

Then Microsoft did a silly, silly thing.

It moved the update from 'optional' to 'recommended' and anyone who reads this site regularly will know what happens when Microsoft does this. That's right boys and girls - it makes it automatically install, unless you've specifically told your machine not to.

So now, if you have one of the affected motherboard and you keep your security updates automatic like wot Microsoft recommends, then your machine will stop working properly.

We should add it's not permanently bricked, but it will take some mucking about in the BIOS to fix and that's a pain even for an experienced computer user.

Microsoft has, by offering a workaround, suggested heavily that it won't be fixing the problem, though we have asked the question, so expect a response in about a fortnight.

But the real kicker is this piece of advice: "Note The Secure Boot feature is supported in Windows 10. To learn more about the security advantages of this feature and about the upgrade path from Windows 7 to Windows 10, go to the following Windows website"

Holy toledo, this company really knows how to rub people up the wrong way.

After all - if the advice is to manually avoid the update or move to a version of the operating system where there's virtually no control over updates, then Microsoft is dealing in massive contradictions.

A more cynical site would suggest that it's yet another example of Microsoft running Windows 7 into the ground and adding built in obsolescence to encourage quicker updates. But we're not that sort of site.

Its the patching to force secure boot that is the problem win 7 does not support secure boot
hence it borks systems and well microsofts answer is Cactus >your Asshole > insert

from the inquirer