[INFO - DISCUSSION + Downloads] Windows 10 1809 FINAL b 17763.xxx (PC) [RS5]

Admin rights requirement for DISM and path space issue.

Spoiler

Code:

<!-- : Begin batch script
@echo off
if [%1]==[] goto quit

::=============================

fsutil dirty query %systemdrive% >nul || (
cscript //NoLogo "%~f0?.wsf" //job:ELAV /File:"%~f0" "%~1" && exit /b
) || (
echo Elevation failed.
goto quit
)

::=============================

echo.Mounting... %~nx1
for /f %%L in ('powershell.exe "(Mount-DiskImage '%~1' -PassThru | Get-Volume).DriveLetter"') do set L=%%L
dism /Get-WimInfo /WimFile:%L%:\sources\install.wim /index:1
dism /Get-ImageInfo /ImageFile:%L%:\sources\install.wim
echo. & echo.Unmounting image... & echo.
powershell.exe "Dismount-DiskImage -imagepath '%~1'" >nul 2>&1
:quit
echo.Press any key to exit... & pause >nul

::=============================

: ======================================================
:  [VBS and Batch] Elevate program as admin with full
:  arguments and special chars (incl Quote), no TMP.
:
:  https://forums.mydigitallife.net/threads/.74332/
:  Written by @hearywarlot (MDL)
: ======================================================

----- Begin wsf script --->
<package>
   <job id="ELAV">
       <script language="VBScript">
           Set strArg=WScript.Arguments.Named
           If Not strArg.Exists("File") Then
               Wscript.Echo "Switch /File:<File> is missing."
               WScript.Quit 1
           End If
           Set strRdlproc = CreateObject("WScript.Shell").Exec("rundll32 kernel32,Sleep")
           With GetObject("winmgmts:\\.\root\CIMV2:Win32_Process.Handle='" & strRdlproc.ProcessId & "'")
               With GetObject("winmgmts:\\.\root\CIMV2:Win32_Process.Handle='" & .ParentProcessId & "'")
                   If InStr (.CommandLine, WScript.ScriptName) <> 0 Then
                       strLine = Mid(.CommandLine, InStr(.CommandLine , "/File:") + Len(strArg("File")) + 8)
                   End If
               End With
               .Terminate
           End With
          CreateObject("Shell.Application").ShellExecute "cmd", "/c " & chr(34) & chr(34) & strArg("File") & chr(34) & " " & strLine & chr(34), "", "runas", 1
       </script>
   </job>
</package>

 

That's not a solution though I already on the latest v1903 18262.86 since the end of March in most of my systems. One of my primary systems is still in v1809 where this issue persisted, as I can't get rid of this error so it seems clean installation is the only option left so I'll be doing that next Tuesday eventually, i.e. patch Tuesday & (probably) the GA of v1903 with another latest CU.

 

Its probably too aggressive and time consuming to bother with but I had a similar situation a while back and did 2 things that got the install sorted.

First I ran Tweaking.com - Windows Repair under NSudo.exe.

After reboot I installed windows on top of itself with the latest updates integrated.

After that completed all future updates worked without a hitch.


The NSudo.exe part actually ended up being important as I tried this once without it and the upgrade install failed and reverted.

 

Today I upgraded that system to 19H1 too as I didn't find any solution after tried & tested everything.

 

Is this the final build (18362.30) that will be released to the public later this month?

 

Thank you op. I'm new here, adjusting to the place. Will I miss anything between this release and the official?

 

No, if you follow the 18362 thread.

 

You need to login to view this posts content.

 

i am still waiting for RS5 major update , and has paused updates for 35 dates after .107 base fresh install on a new SSD .

 

I noticed that KB4494441 install twice today. After the updates I cleaned up system files and reboot. Then after a while this kb has been downloaded again and installed a second time. Strange isn'it ?

 

I am on version 1809, I got KB4494441 update, now I am on build 17763.475?
Edit: Just saw Enthousiast post, now updating a 2nd time.

 

So I was on 1803 for the longest of time and now because of this new Intel Flaw I had to go into updates.. Surely enough M$ forces me onto 1809 even though 1903 is right around the corner.

FU M$ and Craptel!

 

anyone having this issue after updating to May 14, 2019—KB4494441 still shows the OS OS Build 17763.475

 

never mind WU force me to install twice....classical MS

 

I also had to install update twice.