Download Windows Image

0 views
Skip to first unread message

Dashonn Moulton

unread,
Aug 5, 2024, 9:41:55 AM8/5/24
to tranathtilen
Yesi try once this software, but i prefer to look at open-source software, because commercial software if have free version its doesnt mean that developers in one day make it only paid system, and in this case if you used to this software you need or buy it or look for another software.

Windows Backup from what I recall only keeps 1 image level backup in the target folder. But if you set up a Duplicati backup job specifically to protect that target folder, you can set your own retention options in order to keep multiple versions and for longer periods of time.


Well, i will try soon find open-source solutions for my requirement. I can use wbadmin ofcourse, but its not user-friendly, cmd format, so need use batch files with task scheduler. If duplicati cant use own instruments to make system image backup, maybe developers should use module in duplicati, that module can run builtin windows tool wbadmin?


I use a combination of Windows Back-up and Duplicati. WB gives me the windows image and Duplicati handles the rest (dedupe, upload, scheduling, etc.). If you feed the WB images from similar systems (i.e. same OS) to Duplicati, it will give you a very good dedupe rate.


I am trying to run my java application in windows container.I have been succesful in making docker image and running it.

My concern is size, I am new to docker so I may be wrong in understanding this.

The base Image of microsoft\windowscoreserver has size of 8 gb when I see through docker images.

Once I build my image using windowsservercore, the size reaches 9.2 GB.

Is it valid, why would someone deply an image that is 9GB in size and rather not choose VM over it.

Is there something that I am doing wrong.


The other base layer option is Nano Server, a new and very minimal Windows version with a pared-down Windows API. Lots of software already runs on Nano Server, including IIS, the new .NET Core framework, Node.js and Go. And the Nano Server base image is an order of magnitude smaller than Windows Server Core, meaning it has less dependencies and surface area to keep updated. Nano Server is an exciting development, not only as a base for minimal containers that build and boot quickly, but also as a Minimalist Operating System that makes for a great container host OS running just the Docker daemon and containers, and nothing else.


To be honest in a domain environment you do not want to spin up a very old backup. you would want to access files only, and not the full OS. This is even more critical if you have multiple domain controllers. You may end up in a more work than starting fresh and migrating. It really depends on your directory structure and amount of files.


I have had success with this before. However to echo previous replies you do not want to spin up an old backup, if you do what we do and have them backing up on a daily basis then its not that bad. Simply copy and paste the VHDX files to a hyperV host and create a VM but you will need to attach all hard drive images the system partition and C drive to make it bootable.


I had an instance a few months ago where I had to do a recovery from a VHD image of a SQL server data drive. I simply attached the VHD file to an already live virtual machine and was able to restore from it.


I would like to apply a specific analysis on a window based on its name. I have several windows open and would like the macro to select the ones that should be analyzed. So far, the macro is always stopping after the analyze of the last selected window.

The windows are duplicates of ROIs of different planes of a bigger vsi file and there are not in a directory.

How can I get the macro reading all the windows that should be analyzed?


Can you try to add selectWindow(list[i]); at the start of your first for loop? This should focus each window in turn so that when you start thresholding, the correct window is selected (not just the one in front). Something like:


Repair a Windows image using DISM. You can repair offline Windows image in a WIM or VHD file, or an online Windows image. An online Windows image will also attempt to repair itself if it becomes unserviceable. The repair source for this operation is the same source that is used for Features on Demand and is determined by Group Policy settings. For more information, see Configure a Windows Repair Source. When you use the DISM tool to repair an online or offline image, you can use the /Source argument with the /RestoreHealth argument to specify additional repair source locations to use to search for the required files.


When you use the /CheckHealth sfc argument, the DISM tool will report whether the image is healthy, repairable, or non-repairable. If the image is non-repairable, you should discard the image and start again. If the image is repairable, you can use the /RestoreHealth argument to repair the image.


If you do not specify a /Source for the repair files, the default location for Features on Demand is used. For more information, see Configure a Windows Repair Source. If you specify more than one /Source, the files are copied from the first location where they are found and the rest of the locations are ignored. You can use /LimitAccess to prevent the DISM tool from using Windows Update as a repair source or as a backup repair source for online images.


In some cases, an image can be corrupted while modifying it with DISM. Use /Cleanup-MountPoints to repair it. This command will not unmount images that are already mounted, nor will it delete images that can be recovered using the /Remount-Image command.


Hi @Darshan Rajput,



Welcome to the community.



Unfortunately, we don't support native Windows .NET images on Bitbucket Cloud Pipelines.

However, we've recently released the feature called Bitbucket Cloud Pipelines Windows Runners which will allow you to run your native Windows builds on your self-hosted machine.


I've created a system image on an external hard drive and I was hoping to restore from it. Problem is all the tutorials I've seen only explain how to restore from a CD/DVD, for example -windows-7-from-an-image-backup/


I followed the suggestion below to get to the Repair my computer screen but I get the message the boot selection failed because a required device is inaccessible. My HD is formatted to ntfs. Could this be a problem? I swear this should be more straight forward...


Sorry, the system image was stored to an external drive - which is not bootable. You can't start the computer from that drive in order to get access to the image file. When you created the image, did you make the system restore disk as well? You boot the computer from the system restore disk and then search for the image to restore from.


When you are just about to start installing Windows, at the screen where you choose Install there should be an option that says "Repair My Computer". Click on the "Repair My Computer" link and that is how you access the part of the installer where you can restore from your system image on the external hard drive.


I installed Windows 10 via Boot Camp some months ago when my main OS was Sierra. After the small partition space filled up quickly, I decided to save my complete instance of Windows 10 through a backup, and a system image (by which time I had already upgraded to High Sierra). These files were placed on an external hard drive.


I removed my Windows 10 partition via Boot Camp Assistant, and did a clean reinstall with a larger partition. From this point, I realized I needed to use the Windows Media Creation to boot the restore from, so I used a USB flash drive for this purpose.


Now, I boot my MacBook (while holding opt/alt), select the EFI USB flash drive to boot from, go to the system image recovery, load my external hard drive, and it even shows the backed up system image, however I'm getting a message that says:


"To restore this computer, Windows needs to format the drive that the Windows Recovery Environment is currently running on. To continue with the restore, shut down this computer and boot it from a Windows installation disc or a system repair disc and then try the restore again. If you don't have a system repair disc, you can create one now."


Windows 10 is fully installed, and I am getting the same message when I try to restore from within Windows (Settings>Update & Security>Recovery>Advanced startup). I will attach the message error below. (Could not rotate the picture sorry).


The problem is due to High Sierra. Under Sierra, you computer would have used BIOS. Apple does not seem to have rigorously tested HS on older Macs. The late 2013 and 2014 Macs can support either mode.


Use BCA to remove the current installation on the internal disk, and use BCA to install a new copy. Can you look at Bootcamp User Interface and tell me which of the three styles do you see? I expect the Create-Download-Install UI.


Create a FAT partition using Disk Utility, and install GPT Fdisk ( ) and if the hybrid MBR is missing, use the Rebuild MBR section from Re: El Capitan has deleted my bootcamp windows partition as a reference to create one.


Windows System Image restore assumes that it owns the entire hard disk, not just the designated partition. You need to fully install W10 on the larger partition, and then use the restore function, not using the installation media.


So I would have to delete my High Sierra partition, and have a sole OS of Windows 10 on my MacBook? Is this possible? Also, what kind of problems could I potentially run into, and how big of a risk is it? I'm trying to avoid having to re-install my applications and settings on my new Win10 partition as much as possible, but will if there is no safe workaround.


I have the exact same issue!

I would be so grateful if anyone has a solution to this...

Why does windows need a CD/DVD with the OS iso on it, when it is already on the USB drive ? ?......

Is there any way to restore my system image from my external hard drive?...


You do not need a CD/DVD disc, but you do need to build a Windows Recovery USB disk when the installation has not been restored. Once you build it, then you can try and restore, but be careful, because if it wants to erase the destination disk, you will lose macOS.

3a8082e126
Reply all
Reply to author
Forward
0 new messages