If this is your first visit, be sure to check out the FAQ by clicking the link above. You may have to register before you can post: click the register link above to proceed. To start viewing messages, select the forum that you want to visit from the selection below. |
|
|
Thread Tools | Rate Thread | Display Modes |
#1
|
|||
|
|||
Still unable to update to 1903
MSI Laptop I7 processor +NVIDIA Graphics ... still unable to update
from 1809 (17763.615) to 1903. Install runs to 72% and then just fails with the inclusive result 80070003. I've tried Dism and SFC, both run OK. Any suggestions welcome. |
Ads |
#2
|
|||
|
|||
Still unable to update to 1903
Oldster wrote:
MSI Laptop I7 processor +NVIDIA Graphics ... still unable to update from 1809 (17763.615) to 1903. Install runs to 72% and then just fails with the inclusive result 80070003. I've tried Dism and SFC, both run OK. Any suggestions welcome. If that was my machine, I'd be looking in the BIOS to see if I could switch down to Intel-only graphics (of your Optimus Intel/Nvidia setup) until the install was finished. Then try switching NVidia on again. I hope you have a backup. The install phases are documented here, but without percentage ranges printed on the page to aid in identifying it really is the driver phase that is failing. https://docs.microsoft.com/en-us/win...upgrade-errors You can see a "sub" error code there, identifies the phase. 0x2000c, 0x20017 === Apply Drivers is in this phase. 0x30018, 0x3000D 0x4000D, 0x40017 Maybe it really isn't drivers then, as 72% is too far along. Presumably the first phase doesn't need those codes, because the OS never gets to reboot in that phase. Rollback could happen before any reboot. Just out of curiosity, are you one of those people who move Program Files to D:\Program Files or moved C:\users\oldster to D:\users\oldster ? As sometimes moving portions of the install, the installer cannot handle the variations (it doesn't check for that in a useful way). Paul |
#3
|
|||
|
|||
Still unable to update to 1903
Oldster wrote:
MSI Laptop I7 processor +NVIDIA Graphics ... still unable to update from 1809 (17763.615) to 1903. Install runs to 72% and then just fails with the inclusive result 80070003. I've tried Dism and SFC, both run OK. Any suggestions welcome. In this thread, they mention that Easeus Partition Manager can screw up some IDs on disk partitions, and that causes a 80070003 "because something cannot mount". https://www.tenforums.com/installati...llation-2.html https://www.eightforums.com/threads/...58/#post429799 I wish I could be sure about these error numbers. Paul |
#4
|
|||
|
|||
Still unable to update to 1903
On 29/07/2019 15:27, Oldster wrote:
Any suggestions welcome. People have used IT Technicians to get this done swiftly so perhaps you could try it. They only charge 50 bucks for their work (in your case £50.00 in new money when we get pound, shilling and pence after Brexit). Life is unbearable without 1903 so the money is worth spent IMO. Path: aioe.org!news.dns-netz.com!news.freedyn.net!newsreader4.netcologne.d e!news.netcologne.de!peer02.ams1!peer.ams1.xlned.c om!news.xlned.com!peer01.am4!peer.am4.highwinds-media.com!news.highwinds-media.com!fx28.am4.POSTED!not-for-mail Newsgroups: alt.comp.os.windows-10 X-Mozilla-News-Host: news://news.virginmedia.com:119 From: Oldster Subject: Still unable to update to 1903 User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:60.0) Gecko/20100101 Thunderbird/60.8.0 MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8; format=flowed Content-Language: en-GB Content-Transfer-Encoding: 7bit Lines: 4 Message-ID: X-Complaints-To: http://netreport.virginmedia.com NNTP-Posting-Date: Mon, 29 Jul 2019 14:27:59 UTC Organization: virginmedia.com Date: Mon, 29 Jul 2019 15:27:59 +0100 X-Received-Bytes: 1053 X-Received-Body-CRC: 846241964 Xref: aioe.org alt.comp.os.windows-10:95835 -- With over 999 million devices now running Windows 10, customer satisfaction is higher than any previous version of windows. |
#5
|
|||
|
|||
Still unable to update to 1903
|
#6
|
|||
|
|||
Still unable to update to 1903
Oldster wrote:
MSI Laptop I7 processor +NVIDIA Graphics ... still unable to update from 1809 (17763.615) to 1903. Install runs to 72% and then just fails with the inclusive result 80070003. I've tried Dism and SFC, both run OK. Any suggestions welcome. OK, I found something I think you'll find amusing. https://docs.microsoft.com/en-us/win...rade/setupdiag "About SetupDiag Current version of SetupDiag: 1.5.0.0 https://go.microsoft.com/fwlink/?linkid=870142 507,056 bytes SetupDiag is a standalone diagnostic tool that can be used to obtain details about why a Windows 10 upgrade was unsuccessful. Double-click the "SetupDiag" file to run it When SetupDiag finishes, two files will be created in the same folder where you double-clicked SetupDiag. One is a configuration file, the other is a log file. Use Notepad to open the log file: SetupDiagResults.log. " The 80070003 is "file not found" and who knows, maybe they'll be able to tell us which file ??? I had to search Google with "80070003 file not found", to get confirmation that just maybe, that's what the error means. Paul |
#7
|
|||
|
|||
Still unable to update to 1903
On 29/07/2019 15:56, Paul wrote:
Oldster wrote: Â*Â*Â* MSI Laptop I7 processor +NVIDIA Graphics ... still unable to update from 1809 (17763.615) to 1903. Install runs to 72% and then just fails with the inclusive result 80070003. I've tried Dism and SFC, both run OK. Any suggestions welcome. If that was my machine, I'd be looking in the BIOS to see if I could switch down to Intel-only graphics (of your Optimus Intel/Nvidia setup) until the install was finished. Then try switching NVidia on again. I hope you have a backup. The install phases are documented here, but without percentage ranges printed on the page to aid in identifying it really is the driver phase that is failing. https://docs.microsoft.com/en-us/win...upgrade-errors You can see a "sub" error code there, identifies the phase. 0x2000c, 0x20017 === Apply Drivers is in this phase. 0x30018, 0x3000D 0x4000D, 0x40017 Maybe it really isn't drivers then, as 72% is too far along. Presumably the first phase doesn't need those codes, because the OS never gets to reboot in that phase. Rollback could happen before any reboot. Just out of curiosity, are you one of those people who move Program Files to D:\Program Files or moved C:\users\oldster to D:\users\oldster ? As sometimes moving portions of the install, the installer cannot handle the variations (it doesn't check for that in a useful way). Â*Â* Paul No. I haven't moved any of those folders. |
Thread Tools | |
Display Modes | Rate This Thread |
|
|