I try to update my windows but I got this message:
I tried to reboot service but it didn't work.
Current version of my laptop: Version 1709 (OS Build 16299.192)
I am afraid this will be affected to future releases.
I recently had a similar problem on my PC and my laptop. My error code was as follows:
2018-08 Update for Windows 10 Version 1709 for x64-based Systems (KB4023057) - Error 0x80070643
After much kafuffle and reading quite a few articles and Microsoft waffle pages I decided to do it my own "straightforward" way. This is my story, if it helps you I am content. Summary:
Close/save all open applications;
Run Windows Update TroubleShooter;
Find the latest Cumulative Update;
Run the Cumulative Update;
Allow the computer to do the necessary restart processing.
The description below is what I did. It worked both times for me; firstly on my PC and secondly on my laptop. The difference with my laptop was that I didn't repeat the download of the Cumulative Update as I had already done this for the PC, I just ported the Update to the laptop via USB; everything else was the same.
On the laptop the whole process took about 40 minutes, start to finish. I didn't time it on my PC as I was doing things in slow stages. The download of the update is quite large (900Mb) so watch out for download charges if your ISP makes you pay for such things.
All descriptions/statements below apply solely to me. I am describing what I did and what I think. Like with Microsoft and others, any decision by you to follow any aspect of my description is entirely at your own risk. For any "lawyers" out there, any reference to "you" or implications that I am telling you what to do is just an unintended flaw in my poor English grammar.
Save and close all the applications that are being used:
The Cumulative Update will requires a restart of the computer so, for me, it was best to save any data now and close all the applications I had open in an orderly manner.
Find and run the Windows Update TroubleShooter:
Search the web for "Windows Update TroubleShooter". The page I ended up on was this:
https://support.microsoft.com/en-gb/help/4027322/windows-update-troubleshooter
Click the appropriate download link on this page. I am running Windows 10 (Version 1709; x64) so, for me it was: "Download Troubleshooter for Windows 10"; it was a small file, around 200Kb.
The download file was "wu170509.diagcab". I always "Save > Virus check > and then run".
Run the Troubleshooter (I double-clicked it);
On its first page, click "Advanced", then ensure "Apply repairs automatically" is checked, and finally click "Run as administrator". It reloads itself, click "Next" and let it run.
Whenever it found a problem I chose the "Apply this fix" option.
When it reports that it has completed, close the TroubleShooter.
This took me about 10 minutes to do (I am slow and I was also trying to make a cup of tea!).
Find the computer's details:
Load the Settings page; right-click the Windows "Start" icon -> Settings -> System -> About.
Note the following:
Under Device Specifications, note the System Type (mine is 64 bit "x64")
Under Windows Specifications, note the Edition, Version and OS Build details.
Find and run the Microsoft Update Catalogue:
Open a browser (mine is Internet Explorer) in Admin mode ("Run as Administrator" from its icon's Context Menu - I don't know why you have to do this but you get an error otherwise on IE);
Search the web for "Microsoft Update Catalogue"; the page I ended up on was this:
https://www.catalog.update.microsoft.com/home.aspx
Search for the latest Cumulative update for your version. I entered the following search terms that relate to my system in this year "2018 cumulative update windows 10 1709 x64";
Top of my returned list (the latest cumulative update) was:
2018-09 Cumulative Update for Windows 10 Version 1709 for x64-based Systems (KB4464217)
Note its KB number and click on its Title.
An "Update Details" window opens; click on the "More Information" link and a web page opens, mine was:
September 17, 2018—KB4464217 (OS Build 16299.666)
Verify the KB number with the Microsoft Catalog number just to make sure.
I only proceeded with this Update because its Build Number was greater than my current one (from section 3 above); for me, going backwards sounds like a route to a bigger mess.
Once I was content I was going forward I went back to the Microsoft Catalog (closing web pages and windows as necessary) and clicked the "Download" link for this Cumulative Update (KB4464217); a "Download" window appears. Click the link to download it (it says 863Mb). My download took 5 minutes via an Ethernet connection (no idea on timing regarding a WiFi download).
Run and check the Cumulative Update:
When the download had completed (and after virus checking it), I opened its folder and double-clicked the file therein and let it run. It took about 30 minutes to do its work. Once started it needed no help from me so I wandered off and did other work.
Once the Cumulative Update had completed I let it do its necessary restart. This is in fact a couple of restarts and took about another 10 minutes to complete.
Once these restarts had completed I loaded my system and did an immediate Windows Update. It returned with no errors and reported that my system was up to date - Yippee!
Notes:
A. There was one difference between updating my PC and laptop. On the PC my Desktop layout was undisturbed, on my laptop the Desktop layout was reset. I have no idea why the difference occurred.
B. In the middle of writing this, when I got to describing the Windows Update TroubleShooter, I decided to rerun the TroubleShooter on my PC. To my surprise it reported errors. I had done nothing of any significance since applying the Cumulative Update and checking it, just some simple Powershell stuff (Microsoft product) and a bit of internet browsing like news and football results (via Internet Explorer, another Microsoft product). It seems to me that Microsoft are screwing up their own Update System! What clever people they are - not.
Good Luck peoples - Pay It Forward.
The following Microsoft forum article suggests that it is a Windows Update glitch:
Update for Windows 10 Version 1709 for x64-based Systems (KB4041994) — error 0x80070643.
The article further suggests that the OP there has the later build of Windows, and that the problem may be suppressed by hiding the update (how-to provided in the linked article).
Related
My company still has a classic asp site that we are working to upgrade to .net. Our entire development team ground to a halt when we upgraded to windows feature 1803 which introduced task view. A single page went from a few seconds to over 8 minutes to load. Since classic asp and VBScript are not popular there was nothing about this on stack overflow.
I found the fix and wanted to leave this info here in case anyone else also is having this issue.
You need to get the vbscript.dll file from a pre-1803 feature branch of windows and copy it to your updated machine. I did this in two locations c:\windows\system32 and c:\windows\SysWOW64. Not sure if both were needed, but my page load time went from 8+minutes to under 10 seconds.
I recommend keeping your original dll just in case.
You will need to change the owner of the file from Trusted Installer to Administrators to grant yourself the permission to touch the file.
I have a Clickonce app from Visual Studio 2015 SP3 that is published to the network server and used in-house only. The program works just fine when launched from Visual Studio. It runs just fine on a Windows machine that does not have the 1803 update. But once a machine updates to 1803, the application no longer starts. I get the "Checking for updates..." window then nothing. On a fresh install, I usually get the Smartscreen telling me the program may be dangerous. It doesn't get that far.
I've created the Clickonce from a computer with the 1803 update and the problem still exists.
I've disconnected the machine from the network. The application starts but then has no database access and it needs the database. It's also written to hide buttons that would use the database to prevent users from trying to do things that require it.
I found a workaround (third paragraph) at https://social.technet.microsoft.com/Forums/en-US/7cbd16f5-526e-4b0b-a186-3ebf41b7b349/smartscreen-prompt-does-not-show-for-clickonce-app-since-windows-10-update-1803?forum=win10itprogeneral. When I start the application from the directory mentioned, I get the Smartscreen and can tell it to run anyway. Every time I click the desktop icon, it works just fine.
If a new release is published, the new release is downloaded and the program updated, but the Smartscreen no longer appears and the application never starts.
So somewhere between installing the latest update and the Smartscreen, this is failing. Anyone else experiencing this and have an idea as to why?
Yes, frustratingly I also experienced this today. Presumably a security update that they'll release another patch for given this is quite a pain for developers and users of small business apps.
Rather than disable Defender or SmartScreen I chose to add my deployment website to the Trusted Sites in Internet Explorer and that then re-instated the warning dialog and my app updated and ran as before.
Really annoying given the nature of the issue and how long it took to figure out, but at the same time I had to use IE today, which is a rare event nowadays.
This works for me...Warn doesnt warn anymore...
After running in the same problem, I just found that my application was going to halt after a stupid uncaught exception.
Despite the fact that the image below is in Portuguese, Event Viewer shows the right error cause.
In my case, was a corrupted settings file!
It appears as though some subsequent Windows Updates have fixed the issue on several of our PC's that were previously experiencing the issue.
Check for the updates listed here.
https://www.catalog.update.microsoft.com/Search.aspx?q=KB4338548
Running winver.exe will show you which build you have.
This may be trip down memory lane. I have been asked to fix some code that was written 8 years ago. That in itself is OK. I have a Win 7 64 bit PC. As I now use VS2012 I had to install 2005 luckily had a copy still. Then all the updates from MS so that it will work with Win 7 64 bit. Create a dummy MFC app to make sure it all works. So far so good. Next I get the SDK to target the code to it is running on a Moxa UC7124 ARM4i. I get UC712XCE_SDK_V2.0.msi and install it.
Now the problem starts. I cannot see the Moxa platform inside VS2005. If I load the solution it comes up with the platform but skips compile. My guess is that VS cannot find the SDK. I have tried many things but obviously not the correct thing yet, I checked for environment variables and find none, registry has no entries.
I look inside Tools | Options under Projects and Solutions VC++ directories but cannot find the platform I only get Win32. So for the first time in a while at the moment I am lost. Has anyone got any ideas why I cannot get the Moxa SDK visible inside VS2005?
After several days progress has been made ....... but not yet fully working. My view was that there must be some permissions issue in Win 7 when trying to load older SDK's, so I uninstalled the SDK first. Next I right click on the SDK's msi and in security tick "run as compatibility" and choose "Previous version of Windows". I can now target my solution correctly. So this part appears to be working now and next I have to fix all the compile/linking issues. Still got a big hill to climb but fingers crossed when I get to deploy this that it is all going to work OK.
So I was one of the unlucky who didn't get the reservation on my PC despite meeting all the requriments.
Now I would like to update to win 10 using the MediaCreationTool by Microsoft.
My concert tho is, would updating the system this way be the same as with the reservation?
Meaning will I get to keep my files, and have the option to go back within 30 days?
I'm running win7 Home Premium x64 SP1
Will be glad for any answer
I've done it and I kept all my files and apps.
I also have Windows Rollback (The option to go back that u mentioned)
I was running win8.1 x64
The best option for me. Open the computer, remove the system Hard drive, and get an empty one installed in the PC or laptop, and then install the new Op System you want to try, do the drivers, updates, put some of your software, and test it for a while. If you don't like it, just change the H Disk for the old one.
I've been assigned to download and install the Windows Logo Kit v1.6 to test a driver for Windows 7. What I have done so far is installed the controller and the studio on a clean Windows 2008 R2 64 bit machine. I also have another clean Windows 7 Pro 32 bit as a client. After the installation, the client machine shows in the Studio.
The next step is to install the driver on the client PC. I've tried googling around to find documentation for this part, but I haven't found any.
How do i install the driver on the client PC? Do i just install it the way I always do or is there a special procedures that I need to follow?
At the studio, there so so many tests to run. How do I know which test to select?
I really don't understand what the problem appears to be, especially since DTM.chm is pretty clear on what to do and how and when. The basic steps if you have set up the DTM controller and clients and registered the clients in a "machine pool" are to open the DTM Studio on the DTM controller and then (quoting the online documentation):
Open Driver Test Manager (DTM) Studio.
On the Explorers menu, click Device Console.
Select View By Submission.
From the Submission control, click New Submission. The Create New Submission Wizard appears.
From the Select OS dialog box, click the Windows operating system that is installed on the client, and then click Next.
From the Select Category window, click ...
... and this is were it depends on your driver class etc. So without a refined question no refined answer.
Anyway, skipping a few steps ahead:
Type the path to the INF file and click Load. You can also use the Browse button to find your INF file.
... this is where you are selecting your - hopefully correct and tested - INF file and the rest again depends on what you want to achieve.
If you have an MSDN subscription you also have a number of support incidents "free of charge" per year, which may be a good idea if you get stuck here. However, so far the documentation was reasonable enough to see us through ...
Note again: the whole process depends on your driver class.
Also note: there is a list of errata (Microsoft's terminology). Make sure those are up-to-date and not expired, because if you have a driver class with special needs, some tests will likely fail and you need to select the errata that apply to your driver then to achieve the 100% result required to get it cross-signed. We don't do the full Windows Logo process, though, but the DTM part should be the same anyway.