11/4/2019 11:31 AM | |
Joined: 6/30/2014 Last visit: 8/28/2024 Posts: 463 Rating: (89)
|
Good day Mr. AlMajidi, I see your issue and feel with you, but, if I were you I would go down this road: --> I'd install the (supported) operating system; that list/matrix, can be seen in the documentation. --> Update it, with all updates which Microsoft offers. --> Use the "FrameSetup" of COMOS, that is the setup.exe on the upperst level of the full version of the mentioned COMOS-Version; doing so, I would run the setup.exe over the right mouse button "Run as an Admin". --> The setup writes some logs on the HDD, maybe you like to have a look into them; I guess that the "UpdateCenter" of COMOS did not worked (copying some files to update the COMOS-Version) due to not enough rights in the operating system itself; I am sure that this is not a bad behavior of COMOS. I see the logs here: In case you see the error1602in those logs, I will say that that is an error code from Microsoft, not from COMOS; you may search for that code with a search engine, for solutions suggestions; but, troubleshooting that error code could be kind of difficult and time consuming, so I would prefer to stay with the workflow suggested here above -->Running the setup.exe on another machine, as a Win-Admin, could show if this issue can be seen on other environments. -->For troubleshooting, to see behind the scenes, you may use the ProcessMonitor, from Microsoft. --> That will surely help, please try that first. --> Of course, in case you need help, you should open a ticket. Attaching the logs will surely help them, also by describing the exact environment which is affected. ~~~> It would be great to hear/see here if you have solved this, if so, how did you solved it. With best wishes, SuperPippo |
Follow us on