WES7 : «Windows cannot access the installation sources. Verify that the installation sources are accessible, and restart the installation»

I try to install Windows Embedded Standard 7 on an empty Compact Flash 4 GB but during installation, I have an error message «Windows cannot access the installation sources. Verify that the installation sources are accessible, and restart the installation.«

I have created an Answer File with Image Configuration Editor and I have created an IBW Image from my Answer File. All files and folders of IBW Image ( 738MB ) are copied on a bootable USB key of 4GB. I have inserted USB key in a computer with a Compact Flash 4GB (which contains only a NTFS primary partition set as Active) and it boots on USB key. IBW Wizard starts and I follow instructions until step of Drive selection. I choose disk and partition of Compact Flash and I press on next button. First 2 steps of installation succeed (Copying Windows Files and Expanding Windows Files) but 3rd step (Installing features and updates) failed with error message «Windows cannot access the installation sources. Verify that the installation sources are accessible, and restart the installation.«.

I have tried doing same thing with a Compact Flash 4GB which contains 2 partitions : a NTFS primary set as active and a system partition but I have the same result. Then I have tried installing it on a Compact Flash 8GB which contains only 1 primary partition set as active and I succeed.

Problem is that I must install it on a Compact Flash 4GB.

Windows installation sources are accessible

Вопрос

I try to install Windows Embedded Standard 7 on an empty Compact Flash 4 GB but during installation, I have an error message «Windows cannot access the installation sources. Verify that the installation sources are accessible, and restart the installation.«

I have created an Answer File with Image Configuration Editor and I have created an IBW Image from my Answer File. All files and folders of IBW Image ( 738MB ) are copied on a bootable USB key of 4GB. I have inserted USB key in a computer with a Compact Flash 4GB (which contains only a NTFS primary partition set as Active) and it boots on USB key. IBW Wizard starts and I follow instructions until step of Drive selection. I choose disk and partition of Compact Flash and I press on next button. First 2 steps of installation succeed (Copying Windows Files and Expanding Windows Files) but 3rd step (Installing features and updates) failed with error message «Windows cannot access the installation sources. Verify that the installation sources are accessible, and restart the installation.«.

I have tried doing same thing with a Compact Flash 4GB which contains 2 partitions : a NTFS primary set as active and a system partition but I have the same result. Then I have tried installing it on a Compact Flash 8GB which contains only 1 primary partition set as active and I succeed.

Problem is that I must install it on a Compact Flash 4GB.

Managing Installation Sources

Users and applications with administrative privileges can retrieve and modify network, URL, and media source list information for Windows Installer applications and patches on the system.

Windows Installer 2.0: Not supported. Administrators cannot read, reorder, or replace entries in the source list and cannot modify or retrieve source list properties. It is possible to manage Network sources, but not URL or Media sources. Administrators can only manage source lists for per-machine applications or applications installed as per-user for the current user. This prevents administrators using versions earlier than Windows Installer version 3.0 from managing source list information for all users in the system.

Windows Installer 3.0 and later: Users and applications that have administrator privileges can retrieve and modify source list information for Windows Installer applications and patches installed on the system for all users. The source list functions can be used to manage source lists and source list properties for network, URL and media sources. The installer can reorder source lists from an external process.

Users and applications that have administrative privileges can read and modify the following types of source list information:

• Source lists for applications and patches installed for all users on the system.
• Source lists for patch sources that exist apart from the application sources.
• Source lists for URL and media sources that exist apart from network sources.
• Source list properties such as MEDIAPACKAGEPATH, DiskPrompt, LastUsedSource, LastUsedType, and PackageName.

The source lists functions can limit the scope of the source lists found by specifying the installation context and user context. There are three possible installation contexts: per-user (unmanaged), per-machine, and per-user managed. The user context can be a particular user or all users on the system.

Non-administrators cannot modify the source list of an instance of an application or patch that exists under another user’s per-user (managed or unmanaged) context. Non-administrators can modify the source lists of an instance of an application or patch installed under the following contexts:

• Their own per-user(unmanaged) context.
• The machine context, but only if the DisableBrowse, AllowLockdownBrowse, and AlwaysInstallElevated policies allows them to browse for an application or patch source.
• Their own per-user managed context, but only if the DisableBrowse, AllowLockdownBrowse, and AlwaysInstallElevated policies allows them to browse for an application or patch source.

Administrators can modify any source list that a non-administrator can modify. In addition, administrators and applications that have administrative privileges can modify the source lists of an application or patch installed under the following contexts:

• Per-machine context.
• Their own per-user (unmanaged) or their own per-user managed context.
• Another user’s per-user managed context.

Users and applications that have administrative privileges cannot modify the source list of an instance of an application or patch installed in the per-user (unmanaged) context of another user.

Managing Network and URL sources for Products and Patches

Use the MsiSourceListAddSourceEx function to add or reorder the source list of network and URL sources for a patch or application in a particular context. Use the dwContext parameter to specify the installation context. Use the szUserSid parameter to specify the user context.

Use the MsiSourceListAddSourceEx function to create a source list for a patch that has not yet been applied to any application in the specified context. This can be useful when registering a patch to have elevated privileges. For more information about registering elevated privileges for a patch, see Patching Per-User Managed Applications.

Use the MsiSourceListClearSource function to remove an existing source for an application or patch in a specified context. Removing the current source for an application or patch forces the installer to search the source list for a source the next time a source is required.

Use the MsiSourceListEnumSources function to enumerate sources in the source list of a specified patch or application.

Managing Media sources for Products and Patches

Use the MsiSourceListAddMediaDisk function to add or update the disk information of the media source of a registered application or patch. Each entry is uniquely identified by a disk ID. If the disk already exists, it is updated with the new volume label and disk prompt values. If the disk does not exist, a new disk entry is created with the new values.

Use the MsiSourceListClearMediaDisk function to remove an existing registered disk under the media source for an application or patch in a specific context.

Use the MsiSourceListEnumMediaDisks function to enumerate a list of disks registered under the media source for an application or patch.

Retrieval and modification of source list information

Use the MsiSourceListGetInfo and MsiSourceListSetInfo functions to retrieve or modify information about the source list for an application or patch in a specific context. Use the dwContext parameter to specify the installation context. Use the szUserSid parameter to specify the user context.

Source list properties such as MEDIAPACKAGEPATH, DiskPrompt, LastUsedSource, LastUsedType, and PackageName can be accessed.

The LastUsedType source list property can only be read. It cannot be set directly using the MsiSourceListSetInfo function.

Clearing the complete source list or forcing a source resolution

Use the MsiSourceListClearAllEx function to remove all the existing sources of a given source type for the specified application or patch instance. The patch registration is also removed if the patch is not installed by any application in the same context. Use the dwContext parameter to specify the installation context. Use the szUserSid parameter to specify the user context.

Use the MsiSourceListForceResolutionEx to clear the last used source entry for an application or patch in the specified context. This function removes the registration of the property called LastUsedSource. This function does not affect the registered source list. Clearing the LastUsedSource registration forces the installer to do a source resolution against the registered sources the next time it requires the source.

Windows installation sources are accessible

Вопрос

I’m trying to install Windows 7 Ultimate onto a computer that is currently running Windows 7 RC. When I attempt to do an «upgrade» I get a not-unexpected error involving the inability to upgrade from the RC.

However, when I attempt to do a clean install, I get the following error:
«Windows installation encountered an unexpected error. Verify that the installation sources are accessible, and restart the installation.

Error code: 0xE000100″

This error happens regardless of if I try to boot from the disk or run the program after the computer has started. What other information would be helpful?

Ответы

You cannot upgrade Windows 7 RC to Windows 7 RTM or Retail version. You can only perform a clean install. The error message may happens if your win7 installation DVD is corrupted. Try to copy all the files from Win7 DVD to local drive then run the setup.exe to perform a custom installation of windows 7. If you even cannot copy the files to local drive, the problem must be caused by the corrupted DVD.

Все ответы

You cannot upgrade Windows 7 RC to Windows 7 RTM or Retail version. You can only perform a clean install. The error message may happens if your win7 installation DVD is corrupted. Try to copy all the files from Win7 DVD to local drive then run the setup.exe to perform a custom installation of windows 7. If you even cannot copy the files to local drive, the problem must be caused by the corrupted DVD.

I’m having the same problem. So far I’ve tried the same Win7Ultimate x64 disc in two different computers with the same result. It gives the error immediately when I click for the clean install. There was something else on the drives, but it should be unreadable by Windows. Perhaps it checks for some free drive space or even some previous version.

I made an RC1 disc to try loading that instead. Same problem. I have never loaded RC1 before.

Right now, I’m running DBAN on the drive. Also I’ll run DBAN in another system.

Will update later.

. Update
I could only get through the install by starting with a clean drive.

Are you saying that I can’t do a clean install? I actually have to wipe my hard drive and then boot the installer from the disk?

In order to keep anything from a previous version, I would set aside that original drive and install Windows7 on a clean drive. That is considering you have a spare drive available.

I could only get through the install by starting with a clean drive.

You have tried a flat installation of Windows 7: Copy all the files from Win7 DVD to local drive then run the setup.exe to perform a custom installation of windows 7.

This method will help you to determine whether the problem is caused by the corrupted disc.

So I took the computer to Best Buy and gave it to the Geek Squad and told them all about it. I got it back 4 days later, and they said that the mobo was bad. I looked at their notes and got the impression that they didn’t really know what was wrong and didn’t want to get in too deep, but a bad mobo would explain some of the weird behavior that that computer has shown recently.

Just for the record, here’s a loose order of events that happened as I tried to install Windows 7:

1. Attempted clean install while Windows 7 RC was running: error 0xE0000100
2. Attempted upgrade while Windows 7 RC was running: Cannot upgrade from Windows 7 RC.
3. Attempted clean install while Windows 7 RC was running: error 0xE0000100
4. Attempted clean install by booting installer from disk: error 0xE0000100
5. Attempted Windows Vista clean install by booting installer from disk: error 0xE0000100
6. Completed Windows XP Tablet factory restore from disk: Windows failed to start because of a missing configuration file.
7. «»
8. Took computer to Best Buy
9. stuff
10. Concluded that the motherboard was bad.