Sorry about the huge title. 
I was recently installing the Windows 7 beta on my laptop using VMWare and ran into the following error:
Windows could not collect information for [OSImage] since the specified image file [install.wim] does not exist.
I was watching Fringe (great show) and tried a few reboots of the Virtual environment during the commercial breaks. When I realized that this method would not work I decided to burn the Windows 7 image file onto a disc (I was trying to install directly from the .iso). To be on the safe side I burnt the .iso at 4X speed and made sure that the disc was verified.
And it worked! So if you get this error one possible solution is to burn the .iso onto a disc at a slow speed.
Hope that helps.
Hi,
May I know how to use this converter correctly?
I always get the below error (during installation of newly created ESD ISO in virtualbox) after converting Windows 7 SP1 x64 ISO(install.wim) to ESD ISO.
«Windows could not collect information for [OSImage] since the specified image file [install.wim] does not exist»
Current OS : Windows 7 SP1 x64
Winreducer Converter : 1.2.1.0
ISO : Windows 7 SP1 x64(install.wim) (size 5GB)
Output ISO : Windows 7 SP1 x64(install.esd) (size 3GB)
Windows 7 SP1 x64 ISO(install.wim) installed fine in virtualbox.
Thank you.
Hello,
Because «install.esd» is not supported by Windows 7 setup installation. Only Windows 8.0, 8.1 and 10 are supported esd file.
So, for Windows 7 you could save your «installl.wim» file in «esd» format : only for backup (but not for use it for setup installation).
In other word, trying to use an «install.esd» file, with Windows 7, will result in a fatal error during setup installation. This is a Microsoft limitation for Windows 7.
And I will improve the detection to avoid such kind of errors.
Anyway, thank you for the report
Hi admin,
Windows 7 ISO can use install.esd for installation too, just that I don’t know how other pple created the ESD ISO.
Thank you.
I think you are wrong … or the support is not officially supported by Microsoft : but if have have information I’m interested (only if this is an official way).
Sorry, I don’t know. Only know it can be done.
Since slipstreaming ISO is getting too big to fix in single layer dvd, so now trying to figure out how those pple create Windows 7 ESD ISO.
Won’t be using other methods(USB install or winreducer to remove) at the moment.
Yes, the USB install should be an excellent solution or may I suggest an alternative solution : instead of slipstreaming your updates in your ISO, just install them after installation, as Windows Updates will work in background task you will be able to install them silently.
you could also splitt your .wim file into .swm files. so you would be able to get it into 2 DVDs
dumbest wrote:
Windows 7 ISO can use install.esd for installation too, just that I don’t know how other pple created the ESD ISO.
Dude;
These guys use a Windows 8 boot.wim to install Windows 7. Otherwise stated, they take a Windows 8 DVD and replace the Windows 7 esd file with the one therein. The installation process starts under Windows setup environment 8 but reverts to Windows 7 after reboot. As winterstorm stated however, this is not an official solution. And this method prevents the use of AutoUnattend.xml you’ve prepared for Windows 7, if there is any. Hope it’s clear now
You cannot reply to topics in this forum
Windows 10: Windows could not collect information for [OSImage] since the specified image file…
Discus and support Windows could not collect information for [OSImage] since the specified image file… in Windows 10 Gaming to solve the problem; I think my Windows install DVD is damaged, can I fix it?…
Discussion in ‘Windows 10 Gaming’ started by Ioannis Pafos, Dec 25, 2024.
-
Windows could not collect information for [OSImage] since the specified image file…
I think my Windows install DVD is damaged, can I fix it?
-
Creating autounattend.xml results in Windows Image Error
Hey,
I have created a autounattend.xml file using the Windows System Image Manager. When validating, everything comes back clean. However, when deploying it ends up failing with the message in the second set
I am deploying using this method to an Intel Compute Stick:- Use Rufus to «install» Windows iso to a Bootable USB drive.
- Drop autounattend.xml into the root of the USB drive
- Boot USB device, let the software do it’s thing.
What actually happens:
- Use Rufus to «install» Windows iso to a Bootable USB drive.
- Drop autounattend.xml into the root of the USB drive
- After a few minutes, Windows Setup complains: «Windows could not collect information for [OSImage] since the specified image file [D:\Sources\] does not exist
A few things about this:
- I never specify D:\Sources anywhere in my autounattend.xml
- Auto
I was not planning on doing this with Sysprep, I was planning on dropping the autounattend.xml file directly on to the root of the USB drive and let it install the image automatically rather than booting through WDS or something similar.
I have been reading Windows 10 Image — Customize in Audit Mode with Sysprep — Windows 10 Forums in case sysprep is the absolutely best way though.
-
Just built A pc and tried installing windows from A usb (I transferred windows from usb from a mac)
Hello I’ve just built A new pc and was trying to get windows 10/11 on it. Stopped by my sisters to download windows off her Mac so I don’t know if there is A difference from A regular pc but once I’ve got home I got the message when installing (windows could not collect information for OSImage since the specified image file (install.wim) does not exist).
-
Windows could not collect information for [OSImage] since the specified image file…
[HELP]Image recovery issues
Guys i am trying to fix my cousins Asus Eee netbook. It has a backup image file that is partitioned on the hard drive but when I go to use it the app will run through a few steps and stop. It is running Vista . Any suggestions?
Windows could not collect information for [OSImage] since the specified image file…
-
Windows could not collect information for [OSImage] since the specified image file… — Similar Threads — collect information OSImage
-
Windows could not collect information for [OSImage] since the specified image file…
in Windows 10 Software and Apps
Windows could not collect information for [OSImage] since the specified image file…: I think my Windows install DVD is damaged, can I fix it?https://answers.microsoft.com/en-us/windows/forum/all/windows-could-not-collect-information-for-osimage/7046754c-8760-4c89-a7de-a37340191eb4
-
The specified file could not be decrypted
in Windows 10 Gaming
The specified file could not be decrypted: Hi Microsoft Support I’m having troubles in accessing my data on D partition, which seems to be partial encrypted. A lot of files, but not all, have a lock symbol next to its icon, after I reinstalled Windows 11 on my computer. To reinstall my Windows, I ran the ISO file… -
The specified file could not be decrypted
in Windows 10 Software and Apps
The specified file could not be decrypted: Hi Microsoft Support I’m having troubles in accessing my data on D partition, which seems to be partial encrypted. A lot of files, but not all, have a lock symbol next to its icon, after I reinstalled Windows 11 on my computer. To reinstall my Windows, I ran the ISO file… -
The specified file could not be decrypted.
in Windows 10 Gaming
The specified file could not be decrypted.: last night I reinstalled window 11 on my laptop login and used the same account as I had last now there are 2 files on the top right corner a lock logo, I can’t access shows their msg every time, and give this erroryou do not have permission to open this file. see the owner… -
The specified file could not be decrypted.
in Windows 10 Software and Apps
The specified file could not be decrypted.: last night I reinstalled window 11 on my laptop login and used the same account as I had last now there are 2 files on the top right corner a lock logo, I can’t access shows their msg every time, and give this erroryou do not have permission to open this file. see the owner… -
The specified file could not be decrypted
in Windows 10 Network and Sharing
The specified file could not be decrypted: Hi, I downgraded by OS from Win 11 to Win 10 Pro and now i am getting an error , » An unexpected error is keeping you from applying properties to the file. Error 0x80071771 — The specified file could not be decrypted». so based on the suggestions already given, i try to take… -
The specified file could not be decrypted
in Windows 10 Gaming
The specified file could not be decrypted: Hi, I downgraded by OS from Win 11 to Win 10 Pro and now i am getting an error , » An unexpected error is keeping you from applying properties to the file. Error 0x80071771 — The specified file could not be decrypted». so based on the suggestions already given, i try to take… -
The specified file could not be decrypted
in Windows 10 Software and Apps
The specified file could not be decrypted: Hi, I downgraded by OS from Win 11 to Win 10 Pro and now i am getting an error , » An unexpected error is keeping you from applying properties to the file. Error 0x80071771 — The specified file could not be decrypted». so based on the suggestions already given, i try to take… -
cmd could not find the file specified
in Windows 10 Drivers and Hardware
cmd could not find the file specified: CMD.exe could not find the file specified and the \ key changes into something else when using[IMG]https://answers.microsoft.com/en-us/windows/forum/all/cmd-could-not-find-the-file-specified/7016e6a0-b14a-46c4-98fe-b64146e3c791
- Joined
- Mar 14, 2023
- Messages
- 59,639
-
-
#2
The error message you are encountering during the Windows 7 installation process typically indicates issues with the installation image file. Here are some steps you can take to address this problem: 1. Check Installation Media: — As you mentioned, downloading the image again and creating a new installation disc might resolve the issue. Sometimes errors can occur during the download or burning process, leading to corrupt installation media. 2. File Integrity: — After downloading the Windows 7 image, verify the integrity of the file to ensure it was downloaded correctly without any corruption. This can often be done using checksum values provided on the download page. 3. Burning the Disc: — When burning the installation disc, ensure that you are using reliable burning software at the slowest speed possible. This helps reduce the chances of errors during the burning process. 4. USB Installation: — Instead of burning a disc, you can create a bootable USB drive to install Windows 7. This method is faster and sometimes more reliable than using optical media. 5. Check Image File: — Double-check the downloaded image file (.iso) to make sure it contains the necessary installation files, including the install.wim file. You can open the ISO using software like 7-Zip to check its contents. 6. Alternative Download Source: — If you continue to encounter the same issue, consider downloading the Windows 7 image from an alternative source to rule out any issues with the specific download. By following these steps and ensuring the integrity of the installation media, you should be able to proceed with the Windows 7 installation without encountering the error related to the missing install.wim file.
I am getting Warning: Unsupported oversized file "./sources/install.esd" detected, this file will NOT be transferred while installing windows iso.
My WoeUSB output:
sudo woeusb -d /home/davut/Downloads/AME20H2.iso /dev/sdb 1 ✘
WoeUSB v5.1.2
==============================
Info: Mounting source filesystem...
Info: Wiping all existing partition table and filesystem signatures in /dev/sdb...
/dev/sdb: 2 bytes were erased at offset 0x000001fe (dos): 55 aa
/dev/sdb: calling ioctl to re-read partition table: Success
Info: Ensure that /dev/sdb is really wiped...
Info: Creating new partition table on /dev/sdb...
Info: Creating target partition...Info: Making system realize that partition table has changed...blockdev: ioctl error on BLKRRPART: Device or resource busy
Info: Wait 3 seconds for block device nodes to populate...mkfs.fat 4.2 (2021-01-31)
mkfs.fat: Warning: lowercase labels might not work properly on some systems
Info: Mounting target filesystem...
Info: Copying files from source media...
Warning: Unsupported oversized file "./sources/install.esd" detected, this file will NOT be transferred.
Info: Installing GRUB bootloader for legacy PC booting support...
Installing for i386-pc platform.
Installation finished. No error reported.
Info: Installing custom GRUB config for legacy PC booting...
Info: Done :)
Info: The target device should be bootable now
Info: Unmounting and removing "/tmp/woeusb-source-20210924-195613-Friday.YB4xTr"...
Info: Unmounting and removing "/tmp/woeusb-target-20210924-195613-Friday.7Vv7xf"...
Info: You may now safely detach the target device
- OS: Manjaro KDE
- Bash: GNU bash, version 5.1.8(1)-release (x86_64-pc-linux-gnu)
- WoeUSB: 5.1.2
Also when i try to click «Install» after i boot the UEFI, it gives the error: Windows could not collect information for [OSImage] since the specified image file [install.wim] does not exist.