Re: Creation Media Tool Windows 10 1809
Vita Strait
After upgrading to VSR21 I cannot create a new bootable recovery disk, so I'm still using an old SSR13. This works so far, but it would be nioce to be able to create a recovery disk that reflects my present system.
Microsoft no longer include the necessary files to create the disk. I have tried the recommendations by Veritas like installing the suggested Windows ADK 10 (Deployment Tool and Windows Preinstallation Environment), but that didn't solve the problem.
5. Proceed the SRD creation wizard.
Note: You do not need to select "Enable LightsOut Restore".
6. Press [Finish].
7. The ISO for SRD is created after the completion of the wizard.
If you experience any issues, please let us know which steps fail and please collect the error messages and screenshots.
When running the SRD creation wizard it stops with a error when creating media. Apparently it cannot access the boot-folder which is hidden, but present as I can access it from a "command prompt" but not through "Windows Explorer" although view is set to show hidden files/folders.
Could you try to create a SRD iso file on another computer? You are able to install the only SRD wizard from VSR 21 install media on the computer. In addition, please install ADK 10 1809 on the computer.
Or please log on as Admin user that has a short name like Admin or VSR. I have seen the similar issue when logging on as a long user name (like xxxxx.yyyyy). The SRD wizard tries to copy files for SRD in C:\Users\\AppData\Local\Temp\.... and it sometimes fails to handle files when the user name is long.
C:\Users\\AppData\Local\Temp\.... is a path that is registered as TMP variable for the user.
I've used the tool many times in the past without any problems but since September I can't get it to work. I've tried media creation tool versions 1903 and 1909. I'm even holding on to old Windows 10 v. 1809 USB sticks because of this.
EDIT: Apparently the problem is with my computer. The same version of the media creation tool and the same usb drive worked fine in another computer. Does anyone know where the log files for the creation tool are stored?
I have trouble upgrading my computer (Surface Pro 1 128GO, bought in 2014 on Windows 8.1 pro in Europe) from Windows 10 Pro 1809 to 1909. Windows Update always return the same error code (0x80070003). I tried to
-free a lot of space
-uninstall Avira
-perform a chkdsk
-try to find what this error code means here but without results
-disable the Windows Subsystem for Linux (I don't have any dual boot on this computer)
-check for Bios update (there is not)
-use the Windows Update Troubleshooter provided here which said there is nothing to fix
-use the windows upgrade tool provided here, which return the same error code
-burn a windows usb flash drive installation from the Media Creation Tools, provided as the same place that above, which still return the same error code.
I have no more ideas, found nothing on the Internet (except that this error code already existed in Windows xp), and Windows 10 1809 will not be maintained any more after the 20 may 2020, and I'm not very "happy" about the idea of making a whole new installation and loose all my software, browsing history and parameters.
But except that, everything works fine on my computer.
Do you have any ideas ?
This is due to the fact Windows is unable mount the required Windows image (*.wim) because your Windows ADK installation changed the value of ImagePath. The SetupDiag tool by Microsoft suggested this was the case.
Use the Disk Cleanup to delete any previous upgrade attempts. A Windows Update Cleanup might also be required. Windows Update history will be wiped by the process but this would happen anyways with a successful upgrade to Windows 10 version 1909.
There are many things that can cause the failure. Assuming that you really want that version of Windows 10 installed. Most likely the easiest way to solve the problem would be to make and install USB or DVD from here
The above tips do not help.
The Update Assistant does not work.
Trying to update from USB ISO with Windows Media Creation Tool, the same error.
I do not have time to do a full reinstallation from scratch.
Please help.
If you do not want to do the full reinstall from the USB media that you created, then turn off auto updates or tell Windows to stop trying the 1809 update. Otherwise, it is going to keep trying as stated in your first post. Sorry, just the way it is. There is a problem either with the software that is already installed or a hardware setup that is causing the update fail. The way I suggested is the only way to stop it, that I know of.
As I stated earlier, I think the only way to get past the problem is a clean install from the Windows 10 tool. You can replace the hard drive and clean install, if you are reluctant to do it with the present hard drive in place. That way there is a "fall back" posotion.
This solution worked for me as well on HP Spectre x360 convertable Windows Developer Mode apparently was blocking the successful install of Version 1809. Uninstalled it and the update completed successfully.
The problem is that when applying ANY theme (WindowBlinds default themes or user customs) the explorer window loses all within the red rectangle (just all inside the red rectangle disappears):
Note that I just wanted to report this specific bug I'm having to make sure Stardock dev. team does not miss this specific bug, since it is not listed in any other customer reports here:
When you ask me to restate the issue I'm facing, it means the issue description I gave is not clear enough?. Then could you please specify what thing exactly is not enough clear? (to try give a better description from my side). See, the problem is just that after any theme is applied in Windowblinds, the entire bottom "pane" (the region I drawn in the red rectangle) of any current and new opened explorer windows it just disappear. I require to unload Windowblinds to restore that bottom "pane".
Ah.. Okay, sorry I misunderstood you. As mentioned previously, the Dev team is working on it now. And I have tested that initial new version. And look like almost all known problems are solved including your status bar issue.
In what meaning it is not stable?, I think the ISO should be a stable release since I downloaded the ISO through the Microsoft's Windows Media Creation Tool. When I published my thread, I ensured which version I'm using by using the ver.exe command-line app.
If you use the media creation tool to download an ISO of Window 10, you will probably get version 17763.1. Some Microsoft servers are still distributing this version as an ISO. 17763.1 has issues and will delete files, user profiles, and sound drivers on some computers. It depends on the type of Windows you are running before you install the upgrade. To the best of my knowledge you cannot download any other version of Windows 10 v1809 17763.1 in ISO form at this time.
Microsoft released a couple of updates to bring 17763.1 to 17763.55. These updates correct previous issues in 17763.1. So you can get the 17763.1 ISO, install it at your own risk, and then download the updates. The other option is to get the ISO and "slipstream" it so that it becomes a version 17763.55 ISO. That is what I did. But a discussion of "slipstreaming" is beyond the scope of this forum.
Thank you @r_pinkard, I have installed version 17763.1 in a V.M. and, while WindowBlinds does not work with this new Windows version, I'm not going to use version 17763.1 as my host OS. I just will wait until I can get the ISO that you suggested (and after ensured WindowBlinds works fine) and then I will replace my host OS.
I'm currently using v17763.55 as a host for 3 Oracle Virtualbox VMs: XP, Windows 7, and Windows 10. Windowblinds 10.65 works fine if you ignore a few things about it. The problem is that it doesn't skin Apps correctly. The min, max and exit buttons are all goofed up. Windowblinds skins "program interfaces" great, but not the apps (including Edge). But then, I don't use apps. I don't believe apps belong in Windows anyway, they are OK on phones, but not in Windows. Going from programs to apps is kind of like going from crayons to pens. Everything looks big and childlike in apps. For example, I hate the calculator app. It's rediculous looking. So I put the old Windows 7 calculator back into Windows 10. It works great. Plus, I hate the photoviewer app. So I put the Windows 7 photoviewer back into Windows 10. The photoviewer is tricky to put back in (an extensive registry hack).
As for the photoviewer that one is easy. Go here and in the middle of the page is a .reg code. Copy it as a text file and name the file photoviewer.reg. It puts the Win 7 and 8 photoviewer back. I've done it and saved the .reg file so I can restore it.
The down side of the insider program a lot of programs won't work with it and companies won't update their programs until the final version comes out. What's the sense of having the insider program when Microsoft doesn't listen to their customers? People complained about problems with the last update and they still rolled it out anyway.
Insider releases are alphas and betas. Sometimes beta means broken. I am currently running Windows 10 v1809 17763.104. The Windowblinds v10.73 beta is working great with it. Even the apps are skinning now. I can't really complain, because I've imported a lot of Windows XP msstyles into Windowblinds format and it's probably a bit unfair to expect these imports to skin all the stuff in Windowblinds 10. But a lot of styles simply vanished from the XP era. Here are a few imports.
The thing is that I need it in ISO/ESD format to load the WIM image and personalize the entire OS with NTLite software.Is not an option for me to install the updates manually after O.S. image personalization, since I will remove unnecessary components from the ISO, like Windows Update.