[SOLVED] [10v1607b14393 x64] Can't upgrade to 1703/1709. No any new driver (0x800703f1)

I get to a point where I see the desktop background without icons and the taskbar without icons as well except for the Windows icons. Clicking on it does nothing or maybe also takes hours.
Maybe it's possible to disable some non-critical services and see if that helps? Or is this a bad strategy?
 
If you hit CTRL-ALT-DEL, how long does it take for the screen to come up with the options for locking, changing password, task manager?
 
This happens immediately. The task manager takes an eternity. I found somewhere on the net that disabling the UX theming can help, maybe this is related. The task manager has a theme, the CTRL-ALT-DEL screen does not.
 
If you are able to copy this entire folder to your USB drive before reverting that would be great.
C:\Windows\System32\winevt\Logs\

Then, yes, I think we need to revert.
 
logs.zip attached. This time I entered the command prompt after the "Hi... we updated your PC" and eventually "This is taking longer than expected..." screens after the update appeared. Perhaps this sheds some light. I can also repeat the procedure after trying to login normally.
 

Attachments

Update: when starting in safe mode and waiting really long I am able to start cmd.exe and explorer.exe which is terribly slow but seems to work.

Edit: I'm event able to enter the Event Viewer via eventvwr from the prompt. I still see this
"The server Windows.Internal.StateRepository.User did not register with DCOM within the required timeout."
every two minutes.
 
That does give some clues, yes! Are you able to boot to a command-prompt and then copy the following file to your USB and then transfer to me?
c:\windows\system32\config\SYSTEM

You may want to send me a PM with this info since there may be private info in it.
 
Thanks for the info. Please do the following.

1. Ensure you copy FRST64.exe on to your USB drive.
2. Also place the attached file on to the USB drive.
3. Reboot into Advanced Options and get to the Command-Prompt
4. Plug in the USB drive into the computer
5. Get to the USB drive. If the USB drive got mapped as D: for example then you can type D: and hit enter
6. Once you are at the prompt representing the usb drive, type frst64 and hit enter.
7. FRST will open. Click fix to perform the fix.
8. Once the fix is done, reboot your computer normally.

Let me know the results.
 

Attachments

The fix applied successfully but the black screen/slowness is still present.
 
OK, save the attached fixlist.txt to your USB drive and run the fix through. Copy the contents of the notepad window that opens and paste them into your next reply. You may have to plug the USB drive into a working machine and then open the contents of the fixlog.txt to retrieve the info and copy/paste.
 

Attachments

Anything else I can try? How do you check for possible registry corruption? Do you have a clean Windows VM somewhere to compare?
 
There are several more things we can try. Let's start with another fix.

1. Ensure you copy FRST64.exe on to your USB drive.
2. Also place the attached file on to the USB drive.
3. Reboot into Advanced Options and get to the Command-Prompt
4. Plug in the USB drive into the computer
5. Get to the USB drive. If the USB drive got mapped as D: for example then you can type D: and hit enter
6. Once you are at the prompt representing the usb drive, type frst64 and hit enter.
7. FRST will open. Click fix to perform the fix.
8. Once the fix is done, reboot your computer normally.

Let me know the results.
 

Attachments

Aha, this accomplished something. After rebooting I saw a dialog "Thank you for updating to Windows 10" pop up which I could close. Then the screen stayed black, but the task manager immediately responded. I was able to open the command prompt as well as the control center or an explorer for a specific directory. The main shell/explorer did not want to come up though, start menu and task bar are still missing. But it's definitely a good step.

I saved new event logs and attached them.
 

Attachments

Let's try the following.

1. Open an elevated command-prompt.
2. Type net user sysnative /add and hit enter
3. Type localgroup administrators sysnative /add and hit enter.
4. Reboot and sign in with the sysnative user. Let me know if you have the same symptoms.
 
Created the user, added it to the Administrator group and logged in. The login itself is pretty quick after a reboot and it even shows the desktop with all icons as well as the task bar. (Same as my regular user now btw even if that takes longer after login). I cannot open the start menu or the control panel though as either user and I keep seeing lots of errors in the event log stating:

AppX Deployment Service (AppXSVC) service depends on the State Repository Service... (I guess this is what we disabled before).

I also get:
Code: 
Faulting application name: ShellExperienceHost.exe, version: 10.0.16299.15, time stamp: 0x59cda974
Faulting module name: twinapi.appcore.dll, version: 10.0.16299.19, time stamp: 0x63553d36
Exception code: 0xc000027b
Fault offset: 0x0000000000094ef5
Faulting process id: 0x1404
Faulting application start time: 0x01d396de029435bb
Faulting application path: C:\WINDOWS\SystemApps\ShellExperienceHost_cw5n1h2txyewy\ShellExperienceHost.exe
Faulting module path: C:\Windows\System32\twinapi.appcore.dll
Report Id: 1c86604b-176d-4106-9d79-3bf6a768900d
Faulting package full name: Microsoft.Windows.ShellExperienceHost_10.0.14393.206_neutral_neutral_cw5n1h2txyewy
Faulting package-relative application ID: App
 
Addition: I was mistaken. My normal user still takes a while to login, 'sysnative' does not.
In the system log I see:

Code: 
The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID 
{6B3B8D23-FA8D-40B9-8DBD-B950333E2C52}
 and APPID 
{4839DDB7-58C2-48F5-8283-E1D1807D0D7D}
 to the user NT AUTHORITY\LOCAL SERVICE SID (S-1-5-19) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool.
 
You must log in or register to reply here.

Has Sysnative Forums helped you? Please consider donating to help us support the site!

Back
Top