I’ve done a Fixlet who copy the iso of windows 10 1709, unzip the iso and then launch the setup.exe with this command :
wait “C:\win10-Update\tmp\setup.exe” /auto upgrade /Quiet /DynamicUpdate disable
But,
It’s working perfectly when I update Windows 7 to Windows 10 1709
It’s NOT working when I update Windows 1607 to Windows 10 1709…
I’ve found a log in “c:$WINDOWS.~BT\Sources\Panther” called setuperr.log
In this I’ve the following errors :
2018-03-16 14:16:47, Error CONX Unable to get message handle 80092009 c:\windows\system32\drivers\fscbapi.sys
2018-03-16 14:16:47, Error CONX Unable to get message handle 80092009 c:\windows\system32\drivers\fscefdmi.sys
2018-03-16 14:16:47, Error CONX Unable to get message handle 80092009 c:\windows\system32\drivers\fscgabi.sys
2018-03-16 14:24:48, Error SP CMountWIM::DoExecute: Failed to mount WIM file C:$WINDOWS.~BT\Sources\SafeOS\winre.wim. Error 0xC142011A[gle=0xc142011a]
2018-03-16 14:24:48, Error SP Operation failed: Mount WIM file C:$WINDOWS.~BT\Sources\SafeOS\winre.wim, index 1 to C:$WINDOWS.~BT\Sources\SafeOS\SafeOS.Mount. Error: 0xC142011A[gle=0x000000b7]
2018-03-16 14:24:48, Error SP ExecuteOperations: Failed execution phase Downlevel. Error: 0xC142011A
2018-03-16 14:24:48, Error MOUPG MoSetupPlatform: ExecuteCurrentOperations reported failure!
2018-03-16 14:24:48, Error MOUPG MoSetupPlatform: Using action error code: [0xC142011A]
2018-03-16 14:24:48, Error MOUPG CDlpActionImageDeploy::ExecuteRoutine(497): Result = 0xC142011A
2018-03-16 14:24:48, Error MOUPG CDlpActionImpl<class CDlpErrorImpl<class CDlpObjectInternalImpl<class CUnknownImpl > > >::Execute(441): Result = 0xC142011A
2018-03-16 14:24:48, Error MOUPG CDlpTask::ExecuteAction(3243): Result = 0xC142011A
2018-03-16 14:24:48, Error MOUPG CDlpTask::ExecuteActions(3397): Result = 0xC142011A
2018-03-16 14:24:48, Error MOUPG CDlpTask::Execute(1631): Result = 0xC142011A
2018-03-16 14:24:48, Error MOUPG CSetupManager::ExecuteTask(2170): Result = 0xC142011A[gle=0x0000013d]
2018-03-16 14:24:48, Error MOUPG CSetupManager::ExecuteTask(2133): Result = 0xC142011A[gle=0x0000013d]
2018-03-16 14:24:48, Error MOUPG CSetupManager::ExecuteInstallMode(810): Result = 0xC142011A[gle=0x0000013d]
2018-03-16 14:24:48, Error MOUPG CSetupManager::ExecuteDownlevelMode(347): Result = 0xC142011A[gle=0x0000013d]
2018-03-16 14:24:48, Error SP CDeploymentBase::CleanupMounts: Unable to unmount the directory C:$WINDOWS.~BT\Sources\SafeOS\SafeOS.Mount. Error: 0xC142011C[gle=0xc142011c]
2018-03-16 14:24:50, Error MOUPG CSetupManager::Execute(237): Result = 0xC142011A
2018-03-16 14:24:50, Error MOUPG CSetupHost::Execute(375): Result = 0xC142011A
Sorry but I didn’t understand or maybe I miss something :
When You get Success with the following task, what kind of KEY did you use?
Task (ID 99767)(K)(Run only when there is no user logged on)(no preset) - Success ( Kaspersky Deleted and then it worked ?)
Task (ID 99767)(Run only when there is no user logged on)(no preset) - Success
4-2.Task (ID 99767)(Run only when there is no user logged on)(no preset)(User Logged in, Waiting, User Logged Off, Running) - Success
For information, my TASK ID is 1100974 (French version) and source release Date is 17.10.2017
That’s great to hear. I’m having a hard time believing its just me. 1703 worked like 99% of the time and if I run the same command in the filxet for 1709 manually, it works 100% of the time… but the fixlet just won’t.
I finally was able to perform an upgrade from 1607 to 1703. I could never get the ISO to prefetch without it either hanging on Pending Downloads or going to Download Failed.
I took out the prefetch block and replaced it with a “continue if” to check that the ISO was on a folder in the C drive, as well as changed the parameter “workISO” to the folder I manually created.
continue if {exists file “C:\1703\en_windows_10_multiple_editions_version_1703_updated_july_2017_x64_dvd_10925340.iso”}
parameter “workISO” = "C:\1703\en_windows_10_multiple_editions_version_1703_updated_july_2017_x64_dvd_10925340.iso" continue if {exists file (parameter “workISO”)}
It ran and reported back as Restart Required, and after restarting it came back as Failed, but it reports back the 1703 build in the OS info, and physically checking it under Settings has the correct build as well. The Action Script Detail shows all steps completed, BES Client log reports it as having been Fixed. Since it fell off of the 1703 action as relevant and I can check the console to see that it actually upgraded, I am not going to get too hung up on having to manually move and it showing Failed.
I am going to use this same method to move my test machine up to 1709. If that works, I will work on the relevance, maybe change it to check the OS build number for relevance
I only tested to update from build 1607 to 1709. If I have a 1703 I will test it and let you know.
I have create my own fixlet for the installation of this update.
I copy the ISO with Software distribution, unzip it with 7zip, check if all files are OK, then apply the update. The only things I see is, when I want to connect to the computer after the reboot, I can’t connect with my domain account, I must use the local account just for the first connection. After that everything seems to be OK, I had one computer who need a windows reaktivation… Don’t know why.
Other thing, I use the same fixlet that I created for upgrading win7 to win10 build 1709, but after update I get the following modification:
-Keyboard layout change ( It’s normaly fr-CH and change to fr-FR)
-Adobe reader is not the default reader anymore
-Edge is default explorer
-Need to do a system cleanmgr to delete the temp folder of the update
-UAC get reactivated
That’s little thing that I can change with a filxet.
I try to do something else now.
We have downloaded the ISO on a relay.
Now we have a fixlet who search on th relay to download the iso on the client computer.
But smb use the current user to acces a net path, how to do a copy from a server without using a net share ? with web server ?
Yes, this is working with windows 7 x64 to windows 10 (Build 1709/1803/1809)
Sometimes there can be problem happen with the parameter
You can try to launche setup manualy and See If you get an error, I hade one time a computer who doesnt want to update because it needed the windows key to install windows 10
Try this(setup.exe /auto upgrade /Quiet /pkey xxxxx-xxxxx-xxxxx-xxxxx-xxxxx)
This will not work if you try to update windows 7 x32 to a windows 10 x64
For that you must use reimage tool
I am having an issue with the Relays and computers sending back a Disk Limit when I try to preposition the package on them. All of them have the HD space and a 100Gb limit on the transfers. The package either ways fails and never starts from what I am seeing in the computer logs.