Windows 10 Upgrade 9252 Download

[Pascale]

Iupgraded the 1909 with the file Windows10Upgrade9252.exe like 6 weeks ago. With the occurring news about problems with the 2004 upgrade, I wanted to at least switch to 1909 with the second one. Sites like cnet.com state that 1809 patches just ended for end users. And I missed to upgrade one laptop before 2004 was made publicly available.

My hidden goal is to get the "last but one" upgrade.

This question about a specific iso points to -adguard.net/ - does that fulfill my hidden goal as well = I just need to get it installed from an USB with that 1909 iso on it? (As I do not iso installs that often I want to add: the currently installed programs need to stay installed, the licence kept etc. ...)

I am using Windows 10. So basically the trouble started when I was using Log4OM, WSJT-X and Gridtracker. I minimized those while talking to some Hams on the Cormac CQ 100 program. While chatting, WSJT-X showed an error "USB Audio not connected", "Soundcard input error" or something of that nature. I closed it and the logging program as well as Gridtracker. Later when I went back to open everything no joy. After opening Device manager I saw my Com port was missing as well as the Audio CODEC. That was the problem. It was not recognizing my Com port or Audio CODEC.

I tried everything including reinstalling the USB driver from Icom. Still nothing and in Device Manager the device (Com port and Audio CODEC) was showing up under "USB Serial bus controllers" and it had a warning icon attached to it. It was not working.

I uninstalled the faulty device (remember, it had a warning symbol next to it) from Device Manager and then disconnected the USB cable. After which I went to add/remove programs and uninstalled the Silicon Driver Program. Just search for "silicon" in the search field of add/remove programs and you'll find it. I restarted the computer for good luck, hi hi.

I was just getting ready to activate Devils Tower for Parks on the Air (POTA) and didn't want to wait. I started with phone (USB) on 20 Meters. So my logging programs would work I had the CI-V cable and I used it for rig control. Handy little cable. I made a bunch of phone contacts on 20 Meters. Yeah buddy!

Eventually I went to the Microsoft website and downloaded the "Windows 10 upgrade 9252" file. It's under the Windows 10 May 2021 update heading. Click the "Update Now" button for the file. When I ran it Windows started a download of the update. It took a while, but eventually finished and told me I needed to restart the computer, which I did. On rebooting it did an upgrade and restarted a couple of times, but after about ten minutes or so, the Windows login screen came up.

I was able to reinstall the Icom USB driver and then connect the cable to my IC-7300. In device manager, eveything was as it should be. I was back up and running WSJT-X. I made another 20 or so contacts on FT-8 and now I can move onto PSK31.

Thanks for the report Rich. Glad you got it all working again. If this problem occurs again, what would be your first actions? do you think doing the Win 10 update first would have resolved the problem? Thanks Bill, AA4R

Hey Lionel,

Good to hear from you and thank you for commenting here. I appreciate the input and happy to hear it. Getting out is something I can do now, so I am going to enjoy it while I can, hi hi.

Best 73,

Rich, K0PIR

This site contains affiliate links, which means that if you click on one of the product links, I may receive a small commission. This helps support the channel and allows me to continue. Thank you for the support!

I have enabled all of the Windows 10 feature updates in the Windows Feature Update Subscriptions page. They are still not showing up in the windows feature updates catalog. I read in multiple places that I have to enable windows feature updates in the " Patch and Feature Update Download Settings" page. I don't have that page. What am I missing? How do I get Windows Feature Updates to work? Thanks.

You could download Windows10Upgrade9252.exe and use an MI to install it - that's what I do. Just be careful, it'll download the IMG locally on the device so try not to do more than 10 per site at a time.

If you have a multi orgs box, you can find the Patch and Feature Update Download settings under the System Org

See here:

Please be aware that you need a SMA and the agents on a current level to have this work since the feature is relatively new.

With the latest build of windows 10, and the toolbox to update windows 10 to newest version is coded for the 2004, I modified the variable to 20H2, and it fails. Anyone have a new tool to run to update windows 10 to 20H2?

Thanks Drew

Was my bad. Found all the ones that were paused and not completing updates silently were due to Trend Micro AV needing to be uninstalled prior to Windows Update allowing upgrade to continue.

Uninstalled the AV, then run your script unattended. WORKED. Many thanks

I'm pretty sure that is the room that has a window cleaning device just off the balcony that causes the obstructed view. It's a large structure that when used, travels down the side of the ship spraying water on the balconies/windows. I recommend changing to another balcony.

Yes...it's a ladder and platform ABOVE your head....doesn't obstruct your view at all. You can see it, but it's not a problem. If there are no other cabins avail. in the category you want, don't fear this one!!!

Negative. Your statement of it being above is not correct. The ladder extends down 3 stories starting on deck 10. This thread has pictures taken from 9254. The ladder is directly in front of the 9252 balcony.

Thankyou everyone for your replies. Looks like we don't have much choice as the cruise is fully booked. From previous we won't be spending a lot of time in the cabin anyway so hopefully won't be a big problem for us.:)

Hi, I'm a long-time IT guy who just started working last week for someone else after many years of being in business by myself. Needless to say, I'm new in their environment and with their tools so this question may simply be a learning issue. For all of the below I followed the steps I found from ESET.

The task for yesterday was to use ERA to first deploy the ERA Agent to all the clients. After a couple of tests I sent the main task off to 64 clients (of which the detail of the results says 26 Denied Access, 40 Failed Task and 38 were successful - not sure how it came up with 104, but that's a different question).

Although each one used the trigger type "As Soon As Possible," each one showed up as Planned: "no" even though the detail showed it was set to run ASAP. Since there was no "Run Now" button like I found with the Server Tasks, each eventually timed out with the error "Failed to start task."

As you seem to be new in ERA6, I will ask basic question: were those clients you targeted client task actually connecting to your ERA Server? Can you see last connection time to be updating? Even if remote deployment task was successful, there may be connection problem. Are clients you targeted software installation task marked as managed in Webconsole?

For each client you targeted client task, in it's client details view you should be able to see task execution details with order of operations that were executed - do you see any specific error there? You have not specified version of ERA you are using, but there should be even possibility to access trace message sent from AGENT that may be indicating problem. In case there will be no history records for task execution, it is possible client not even received task for execution.

Regarding misleading numbers in deployment task results - numbers may be true as for each client, multiple deployment methods are being tested - based on their platform. For example WMI-based deployment may fail on access denied, but "Windows network" deployment targeting the same client computer may be successful. For windows clients, especially those not accessible, there will be 3 failed deployment attempts.

Hi, thanks for the reply! Yes, we just upgraded to ERA6 so I am new. The targets were definitely connecting to the ERA Server, in fact, manually deploying the ESET upgrade on a client is reflected in the Computers tab as managed (and the last connection time to be updated is, well, updating!).

Although I set each task's trigger to run "As Soon As Possible," in the client task information the summary line would say "no" under Planned but each detail line under that would say "Run As Soon As Possible." Since, unlike with the Server Tasks area, there's no "Run Now" button, I couldn't do much except watch them eventually expire. I couldn't find any reason why they won't run.

Also thanks for confirming my guess on the misleading numbers. I'm already finding out that, for whatever reason, sometimes just rerunning a task that gets an Access Denied or Failed Task can cause it to be successful.

If I recall correctly, ASAP triggers will be always marked as not planed - my guess is that planed tasks are those that will be executed later and maybe even repeatedly (CRON based triggers for example).

Could you please check task execution history (documentation) whether you see any progress information for this specific task execution on this client. Normally you should see records like "Task started" and "Task failed".

it is also possible that task finished in the meantime - could you check client computer for product you tried to install using task? Even if task is marked as timeouted after 60 minutes, it may have ended successfully after some time. In case you will be able to access client computer, please try to restart AGENT service only to check whether restart is possible.

Last possibility is to diagnose problems using AGENT's trace.log (see it's location in documentation). In case there won't be any relevant errors, enabling full verbosity and re-running task may be helpful.

3a8082e126