thanks for the uup dump download. Idownloaded the win10 pro script and downloaed the iso and then using rufus to make the install easy for mbr pc . thanks very much. but , I found , advance options of the installation were not working and it shoed error 0xc0430001 erro , instead of memu options. for eg. if i click command prompt, it just closes with error I mentioned. I have written this for fix at windows 10 help forums to which till date, i had not received any reply. Msoft has also not documented this error or fixes and one or two posts still remains without any response. I suddenly thought of the word recovery on the top of this error message, and browsse through each of your files in my folders. therre was a config.ini file, which list the important paramenter. I saw, the winre =0 and also Lucwinre=0,, but the recent roll up updates recently released has so many updates including on boot sectors and recovery. I have seen this as a clue and madelcuwinre to update with "1" and then downloaded the iso from the site. Bingo, now the advanced options are working. i tried command prompt,and i do not know if this update is one of the cause for the unexplained error code . Now it works like a charm. The recovery environment is most important , like the os environment. I also saw, the previously 450 mb, compressed winre.wim, now coccupies about 540 mb. I just saw the size inrease in disk management. I still do not know , if this is the reason for that error , but my advance optikons are now working. thankk you very much.If that is the case, then kindly reconsser enabling winre in the config.ini file. the uup dump is marvelloous one, having all updates. My machine is old mbr machine. i do not know, how to attach a screen shot, i just mention the error code
sir, I have already selected that option in the ISO. It updates the windows not the winre. I presume. There is no problem in Boot menus. But advance options failed with that erraora. I tried bootrec commands and all fixes. If bcd is the cause, then there will be boot problem. I had not had any boot problem. Only on recovery. My pc is older one and there is no secure boot. I do not use bit locker also . there is no safe boot or secure boot menu in bios. It is older Bios supported pc.
Does this mean that if I had created a bootable USB before, I don't have to create a new ISO every time for a new build but just copy and replace the files in the bootable USB? Thanks.
For best practice, create the ISO, next extract the ISO to the bootable USB after removing the old files first. ps, no need to convert complete UUP file sets for just integrating 1 or 2 updates every time. Just use W10UI + updates to update a copy of the source ISO (xxxxx.1 on uup dump* or the lowest released MVS ISO build). * https://forums.mydigitallife.net/posts/1515411
Did you try the usual way, right click the download cmd and select run as admin or just simply doubleclick the cmd, it should ask for admin rights bu UAC.
Yes, that's how I ran the script at first. But I now think that maybe it's a Windows issue, as even the script from the old local uup dump app won't detect admin rights.
I saw a opened command window with the call for the script. Probably tinkered with the rights, is many times the cause for these rights problems. I can't answer to this because i dunno what you mean exactly. But that all aside: Try it this way in a cmd prompt: Code: uup_download_windows.cmd 49127c4b-02dc-482e-ac4f-ec4d659b7547
I ran the script as normal with double click, and right click>run as admin, and accepted the UAC prompt, but the output was the same as in the mage. So then I ran it manually through elevated cmd.exe to show that it was indeed running as admin. I meant this app https://forums.mydigitallife.net/th...11-uups-with-ease.75052/page-243#post-1781105 The command you provided helped me realize where the issue was. I thinkered with powershell some time back and removed it from PATH in favor of pwsh. I only replaced powershell with pwsh in the script and it's currently running. Thanks @Enthousiast
Let's see how far the script runs, the dev replied to me that the script should run ps in more places.
There was at least one error before the converter phase, about 'findstr'. But the script did generate the iso in the end 27928.1.250815-1403.BR_RELEASE_CLIENTPRO_OEMRET_X64FRE_EN-US.ISO Currently installing in vmware Also, with pwsh it has to be ran manually as .\ uup_download_windows.cmd 49127c4b-02dc-482e-ac4f-ec4d659b7547 otherwise it won't work I've added the normal powershell back to PATH to avoid this issue in the future.
I wonder, if the Windows Server for ARM64v8 is available to download on uup dump? I have waited for 3 years because Microsoft said that.