990x.top

Простой компьютерный блог для души)

App Setup Files что это?

Всем даровчик. У нас сегодня тема это App Setup Files — мы должны узнать что это такое. Значит сперва давайте глянем на название App Setup Files, так бы сказать разберем его. Что мы тут видим? Слово App означает приложение, то есть программа. Слово Setup означает установка. Слово Files это я думаю вы и так догадались что файлы. Значит в итоге App Setup Files означает установочные файлы программы, вот такая моя мысль.

Значит есть такое дело, смотрите, это вам нужно знать. Бывает что вы ставите какую-то программу. И эта программа перед установкой распаковывает файлы, и уже потом среди этих файлов есть установочный (что-то типа setup.exe) и он запускается и идет процесс установки. После установки, папка, куда были распакованы файлы — должна быть удалена. Но это не всегда происходит. Я лично такие папки иногда встречал в корне системного диска, например после установки драйверов. Также может быть и после установки Офиса. Нужны ли эти папки? В принципе нет, но я лично их удаляю только после того как переименую, проверю что нет ошибок пару дней, и потом уже спокойно удаляю. Ибо если папку переименовать, то можно считать что вы ее удалили — ведь нет больше папки с предыдущим оригинальным названием.

И вы тут спросите, ну и к чему я это написал выше? А вот смотрите. Есть много программ по очистке системы. Например CCleaner, TuneUp, Glary Utilities.. в общем их много.. и вот в этих программах, когда вы будете чистить комп, то там может быть пункт App Setup Files. То есть этот пункт нужен чтобы очистить установочные файлы, которые были созданы при установке программ и обычно они должны быть не в корне диска или еще где-то, а в папке Temp. Вот вспомнил, кстати OpenOffice сначала спрашивает куда распаковать временные файлы, но не все проги так спрашивают Я вот такой человек.. люблю писать то, в чем уверен стопудово. Я скачал ОпенОфис и запустил установку и все верно, вот он спрашивает куда распаковать установочные файлы (то есть это и означает App Setup Files):

Хотя там и написано что это папка установки, но нет, это именно установочные файлы, которые после установки ОпенОфиса можно удалить! Даже есть кнопка Обзор — можно выбрать папку для этих файлов.

Еще такой вопрос может быть у вас — как удалить App Setup Files? А вот это вопрос хороший. Самому удалять я не советую — ибо можете спутать с тем, что удалять нельзя. Папка ведь как раз и не называется App Setup Files, вот я писал про ОпенОфис — куда он распаковывает файлы? В папку с названием OpenOffice 4.1.5 (ru) Installation Files, но тут важно только упоминание Installation Files, что уже говорит что в папке инсталляционные файлы. То есть тут явно сказано что это установочные файлы. А может быть и не сказано ничего. Поэтому самостоятельно искать такие файлы и удалять — я не рекомендую. А вот использовать программу для чистки компа — рекомендую. Но какая самая лучшая? Мой выбор это CCleaner, но я там не нашел пункта App Setup Files или пункта Установочные файлы программ. Я не знаю удаляет ли она их или нет. Но знаю что пользуется CCleaner много народу и не просто так — она чистит все что нужно и при этом безопасно (ну у меня не было траблов никогда после чистки).

Но возможно что другие проги умеют чистить комп от таких вот файлов установочных, но вы знаете, скорее всего те проги не так популярны как Cleaner, поэтому будьте осторожны ребята.. а то напартачить легко…

В общем ребята, я больше даже знаю что сказать. Был в интернете, искал дополнительную инфу про App Setup Files — но ничего толкового нет

Еще у вас может быт такой вопрос — где искать App Setup Files, где это находится? И я отвечу так бы сказать итоговой мыслью. Еще раз. Подведем итоги — App Setup Files это файлы, которые являются установочными, и они появляются при установке какой-то программы. Эти файлы должны потом быть удалены, но это происходит не всегда. App Setup Files это общее название таких файлов, каждая папка для распаковки установочных файлов создает свою папку со своим названием, у каждой проги это название свое. Поэтому искать в компе App Setup Files тупо нет смысла.

Я кстати у себя в компе, где стоит Windows 7, попробовал поискать App Setup Files — зажал Win + E, в правом верхнем углу вставил App Setup Files и начал ждать, в итоге ноль:

Потом я сделал тоже самое, но искал уже по Setup Files и тоже полный ноль:

Так что такие дела. На этом все ребята. Удачи вам, отличного настроения и будьте счастливы!!

Windows Setup Scenarios and Best Practices

WindowsВ Setup installs the Windows operating system. WindowsВ Setup uses a technology called Image-based Setup (IBS) that provides a single, unified process with which all customers can install Windows. IBS performs clean installations and upgrades of Windows and is used in both client and server installations. WindowsВ Setup also enables you to customize Windows during installation by using Setup answer file settings.

Common Usage Scenarios

Common installation scenarios include performing clean installations, upgrades, and unattended installations.

Custom Installations

The most common scenario for WindowsВ Setup is performing a custom installation. In this scenario, you install Windows onto a computer that does not have an operating system, or has a previous version of Windows. This scenario consists of the following stages:

Run Setup.exe from your Windows product DVD or network share.

Select the Custom installation type.

If you are installing from a previous installation of Windows, WindowsВ Setup creates a local boot directory and copies all of the required WindowsВ Setup files to this directory.

WindowsВ Setup reboots, installs and configures Windows components, and, after installation is complete, launches WindowsВ Welcome.

Custom installations do not migrate any settings or preferences from previously installed versions of Windows. Files from previous Windows versions are copied to a \Windows.old directory. All data from the Windows installation including the Users, Program Files, and Windows directories are saved to this directory.

Upgrades

WindowsВ Setup can also perform upgrades from a supported operating system.

This scenario includes the following stages:

Run Setup.exe on the previous version of Windows.

Select the Upgrade installation type. WindowsВ Setup upgrades the system and protects your files, settings, and preferences during the installation process.

WindowsВ Setup reboots and restores your protected files, settings, and preferences. WindowsВ Setup then launches WindowsВ Welcome.

NotesВ В

• Upgrades are used to upgrade a single computer to WindowsВ 10.
• Upgrades support migrating user data to a new system.
• Upgrades support the following customizations of the Windows image. This is not a change in Windows Setup support policy but instead a clarification:
  • Applying a cumulative (quality) update
  • Applying updates to the servicing stack necessary to complete the feature update (see Servicing stack updates for more information)
  • Applying updates to Setup.exe binaries or other files that Setup uses for feature updates
  • Appling updates for the «safe operating system» (SafeOS) that is used for the Windows recovery environment
  • Adding or removing languages
  • Adding or removing Features on Demand

For clarity, Windows Setup does not support upgrades to a Windows image that has been customized by adding / removing / changing applications, settings nor drivers.

Automated Installations

Automated installations enable you to customize a Windows installation and remove the need for a user to interact with WindowsВ Setup. By using Windows System Image Manager (WindowsВ SIM) or the Component Platform Interface (CPI) APIs, you can create one or more customized Windows installations that can then be deployed across many different hardware configurations.

The automated installation, also called an unattended installation, scenario includes the following stages:

Use WindowsВ SIM or the CPI APIs to create an unattended installation answer file, typically called Unattend.xml. This answer file contains all of the settings that you configure in the Windows image. For more information, see Windows System Image Manager How-to Topics.

From WindowsВ PE, a previous version of Windows, or another preinstallation environment, run Setup.exe with the explicit path to the answer file. If you do not include the path to the answer file, Setup.exe searches for a valid answer file in several specific locations. For more information, see Windows Setup Command-Line Options.

WindowsВ Setup then installs the operating system and configures all settings listed in the answer file. Additional applications, device drivers, and updates can also be installed during WindowsВ Setup. After the operating system is installed, Setup launches WindowsВ Welcome.

WindowsВ Setup Best Practices

The following section describes some of the best practices to use with WindowsВ Setup.

Verify that there is sufficient space for WindowsВ Setup temporary files. If you run setup from a previous version of Windows, verify that there is sufficient space on the disk for temporary WindowsВ Setup files. The space that is required may vary, but it can be up to 500В megabytes (MB).

Previous Windows installations are moved to a Windows.old folder. As a best practice, you should back up your data before you upgrade. If you install Windows over a previous Windows installation, all previous Windows files and directories are moved to a Windows.old folder, including the contents of the Users, Program Files, and Windows directories. You can access your data in the Windows.old folder after WindowsВ Setup completes. If you have additional folders not in the Users, Program Files, or Windows directories, those folders are not moved. For example, if you have a folder that is named C:\Drivers, that folder will not be moved to the Windows.old folder.

Review the Windows Setup log files. If you experience problems during WindowsВ Setup, review the log files in %WINDIR%\panther. You will be able to identify and troubleshoot many issues by reviewing the installation log files. For more information, see Deployment Troubleshooting and Log Files and Windows Setup Log Files and Event Logs.

WindowsВ Setup Limitations

The following sections describe some of the limitations of WindowsВ Setup. Review this section before you run WindowsВ Setup.

Enable UEFI-compatibility mode to install to an UEFI-based computer. On some UEFI computers, you cannot install Windows in BIOS-compatibility mode. You may need to switch to UEFI-compatibility mode.

Applications might require a consistent drive letter. If you install custom applications to your Windows image, install Windows to the same drive letter on the destination computer, because some applications require a consistent drive letter. Uninstallation, servicing, and repair scenarios might not function appropriately if the drive letter of the system does not match the drive letter specified in the application. This limitation applies to both the Deployment Image Servicing and Management (DISM) tool and WindowsВ Setup.

Deploying multiple images to multiple partitions. If you capture and deploy multiple images on multiple partitions, the following requirements must be fulfilled:

The partition structure, bus location, and number of disks must be identical on the reference and destination computers.

The partition types (primary, extended, or logical) must match. The active partition on the reference computer must match that of the destination computer.

Installing Custom .wim files requires a description value in the .wim file. When you create a custom .wim file, WindowsВ Setup requires that you always include a description value. If a .wim file does not include a description value, the image may not install correctly. You can provide a description value when you use the dism command with the /capture-image option. If you install a .wim file that does not have a description value, recapture the image and provide a valid description value. For more information, see the DISM — Deployment Image Servicing and Management Technical Reference for Windows.

NoteВ В For Windows Preinstallation Environment (WindowsВ PE), the version of boot files must match the computer architecture. An x64 UEFI computer can only boot by using WindowsВ PE x64 boot files. An x86 computer can only boot by using WindowsВ PE x86 boot files. This is different from legacy BIOS. In legacy BIOS, an x64 computer can boot by using x86 boot files.

Windows Setup Automation Overview

Use Setupconfig.ini to install Windows

What is a setupconfig file?

Setupconfig is a configuration file that is used to pass a set of flags or parameters to Windows setup.exe. Use this file as an alternative to passing parameters to Windows setup on a command line. This functionality is available in Windows 10, version 1511 and later.

IT pros can use the setupconfig file to add parameters to Windows Setup from Windows Update and Windows Server Update Services.

The different parameters that can be used with Windows 10 Setup.exe are described in this topic.

Setupconfig.ini files can contain single parameters, or parameters and value pairs. Do not include “/” characters, and with parameter and value pairs, include “=” between the two.

For example, you create a Setupconfig.ini with the following. Note that the header [SetupConfig] is required.

This is equivalent to the following command line:

How does Windows Setup use Setupconfig.ini?

Using media/ISO file

If you are running Windows setup from media or an ISO file, you must include the location to the setupconfig file on the command line (“/ConfigFile

”) when running setup.exe. For example:

If you include a parameter on the command line and the same parameter in the setupconfig file, the setupconfig file parameter and value has precedence.

Using Windows Update

If the update is delivered through Windows Update, Windows Setup searches in a default location for a setupconfig file. You can include the setupconfig file here:

Use an answer file while installing Windows

You can automate Windows installation by using an answer file:

Use a USB flash drive

Use a sample answer file or create your own with Windows System Image Manager (Windows SIM).

Save the file as Autounattend.xml on the root of a USB flash drive.

On a new PC, put in the Windows product DVD and the USB flash drive, and then boot the PC. When no other answer file is selected, Windows Setup searches for this file.

Select an answer file

• You can select a specific answer file during installation by booting to the Windows Preinstallation Environment, and using the setup.exe command with the /unattend:filename option. For more information, see WinPE: Create USB Bootable drive.

For sample answer files and a list of settings used to automate installation, see Automate Windows Setup.

Modify an existing installation

Because reboots are required during Setup, a copy of the answer file is cached to the %WINDIR%\Panther directory of the Windows installation. You can modify this file to do any of the following:

Update system and control panel settings without booting the image.

Update an image by preparing the PC to boot to audit mode (see Microsoft-Windows-Deployment\Reseal\Mode).

Update the order in which drivers or packages are installed. (Packages with dependencies may require installation in a certain order.)

Replace the answer file in an offline image

Create a custom answer file in Windows System Image Manager (Windows SIM).

Open an elevated command prompt.

Mount the Windows image.

Modify or replace the file: \Windows\Panther\unattend.xml in the mounted image.

NoteВ В The answer file in the image may contain settings that have not yet been processed. If you want these settings to get processed, edit the existing file rather than replacing it.

Unmount the image.

Test the image by deploying it to a new PC, without specifying an answer file. When Windows Setup runs, it finds and uses this answer file.

Implicit Answer File Search Order

WindowsВ Setup searches for answer files at the beginning of each configuration pass, including the initial installation and after applying and booting an image. If an answer file is found, and it contains settings for the given configuration pass, it processes those settings.

WindowsВ Setup identifies and logs all available answer files, depending on the search order. The answer file that has the highest precedence is used. The answer file is validated and then cached to the computer. Valid answer files are cached to the $Windows.

BT\Sources\Panther directory during the windowsPE and offlineServicing configuration passes. After the Windows installation is extracted to the hard disk, the answer file is cached to %WINDIR%\panther.

The following table shows the implicit answer file search order.

Specifies a pointer in the registry to an answer file. The answer file is not required to be named Unattend.xml.

The name of the answer file must be either Unattend.xml or Autounattend.xml.

Windows Setup searches this directory only on downlevel installations. If Windows Setup starts from Windows PE, the %WINDIR%\Panther\Unattend directory is not searched.

Windows Setup caches answer files to this location for use in subsequent stages of installation. For example, when a computer reboots, Setup can continue to apply the settings in an answer file. If you explicitly specify an answer file by using Windows Setup or Sysprep, the answer file cached to this directory is overwritten with the explicitly specified answer file.

Do not use, modify, or overwrite the answer file in this directory. The answer file in this directory is annotated by Windows Setup during installation. This answer file cannot be reused in Windows SIM or any other Windows installations.

Removable read/write media in order of drive letter, at the root of the drive.

Removable read/write media in order of drive letter, at the root of the drive.

The name of the answer file must be Autounattend.xml, and the answer file must be located at the root of the drive.

Removable read-only media in order of drive letter, at the root of the drive.

Removable read-only media in order of drive letter, at the root of the drive.

The name of the answer file must be Autounattend.xml, and must be located at the root of the drive.

\Sources directory in a Windows distribution

All other passes:

In the windowsPE and offlineServicing configuration passes, the name of the answer file must be Autounattend.xml.

For all other configuration passes, the file name must be Unattend.xml.

The answer file name must be Unattend.xml or Autounattend.xml

Drive from where Windows Setup (setup.exe) is running, at the root of the drive.

The name of the answer file must be Unattend.xml or Autounattend.xml, and must be located at the root of the Windows Setup folder path.

Sensitive Data in Answer Files

Setup removes sensitive data in the cached answer file at the end of each configuration pass.

Important
Because answer files are cached to the computer during Windows Setup, your answer files will persist on the computer between reboots. Before you deliver the computer to a customer, you must delete the cached answer file in the %WINDIR%\panther directory. There might be potential security issues if you include domain passwords, product keys, or other sensitive data in your answer file. However, if you have unprocessed settings in the oobeSystem configuration pass that you intend to run when an end user starts the computer, consider deleting the sections of the answer file that have already been processed. One option when you run the sysprep /oobe command might be to use a separate answer file that only contains settings in the oobeSystem configuration pass.

However, if an answer file is embedded in a higher precedence location than the cached answer file, then the cached answer may be overwritten at the beginning of each subsequent configuration pass, if the embedded answer file matches the implicit search criteria. For example, if an answer file is embedded at %WINDIR%\Panther\Unattend\Unattend.xml, the embedded answer file will replace the cached answer file at the beginning of each configuration pass. For example, if the embedded answer file specifies both the specialize and oobeSystem configuration passes, then the embedded answer file is discovered for the specialize configuration pass, cached, processed, and sensitive data is cleared. The embedded answer file is discovered again during the oobeSystem configuration pass and cached again. As a result, the sensitive data for the specialize configuration pass is no longer cleared. Sensitive data for previously processed configuration passes will not be cleared again. Unless the cached answer file must be overridden, embed the answer files at a location that has a lower precedence.

Important
Because answer files are cached to the computer during Windows Setup, your answer files will persist on the computer between reboots. Before you deliver the computer to a customer, you must delete the cached answer file in the %WINDIR%\panther directory. There might be potential security issues if you include domain passwords, product keys, or other sensitive data in your answer file. However, if you have unprocessed settings in the oobeSystem configuration pass that you intend to run when an end user starts the computer, consider deleting the sections of the answer file that have already been processed. One option when you run the sysprep /oobe command might be to use a separate answer file that only contains settings in the oobeSystem configuration pass.

You can add a command to the Setupcomplete.cmd command script that deletes any cached or embedded answer files on the computer. For more information, see Add a Custom Script to Windows Setup.

Windows Setup Annotates Configuration Passes in an Answer File

After a configuration pass is processed, Windows Setup annotates the cached answer file to indicate that the pass has been processed. If the configuration pass is run again and the cached answer file has not been replaced or updated in the interim, the answer file settings are not processed again. Instead, Windows Setup will search for implicit Unattend.xml files that are at a lower precedence location than the cached Unattend.xml file.

For example, you can install Windows with an answer file that contains Microsoft-Windows-Deployment/RunSynchronous commands in the specialize configuration pass. During installation, the specialize configuration pass runs and the RunSynchronous commands execute. After installation, run the sysprep command with the /generalize option. If there is no answer file in a higher precedence than the cached answer file or an answer file was not explicitly passed to the Sysprep tool, Setup runs the specialize configuration pass the next time that the computer boots. Because the cached answer file contains an annotation that the settings for that configuration pass were already applied, the RunSynchronous commands do not execute.

Implicit Answer File Search Examples

The following examples help describe the behavior of implicit answer file searches.

Answer Files Named Autounattend.xml are Automatically Discovered by Windows Setup

Create an answer file that is named Autounattend.xml that includes settings in the windowsPE configuration pass.

Copy Autounattend.xml to a removable media device.

Configure the BIOS of your computer to boot from CD or DVD.

Boot the Windows product DVD.

Insert the removable media device when Windows is booting. This example assumes that the removable media is assigned the drive letter D:\.

Windows Setup starts and automatically identifies Autounattend.xml as a valid answer file. Because the answer file uses a valid file name (Autounattend.xml), is located in one of the valid search paths (the root of D), and includes valid settings for the current configuration pass (windowsPE), this answer file is used.

The answer file is cached to the computer. If there are no additional answer files discovered in later passes, the cached answer file is used throughout Windows Setup.

Answer Files are Discovered in Order of Precedence in Predefined Search Paths

Install Windows with an answer file by using the steps in the previous scenario. The answer file that is used to install Windows is cached to the system in the %WINDIR%\Panther directory.

Copy an Unattend.xml file to the %WINDIR%\System32\Sysprep directory.

This answer file has settings in the generalize configuration pass.

Run the sysprep command with the /generalize option to create a reference image.

Because the %WINDIR%\System32\Sysprep directory is in the implicit search paths, the answer file copied to this directory is found. However, an answer file that was used to install Windows is still cached on the computer and contains settings for the generalize configuration pass. This cached answer file has a higher precedence than the one copied to the Sysprep directory. The cached answer file is used.

Note
The Sysprep tool can be run as a command-line tool or as a GUI tool. If you run the Sysprep tool as a GUI tool, you can select the Generalize check box.

Answer Files Must Include a Valid Configuration Pass

Copy an Unattend.xml file to a removable media device.

The Unattend.xml file has settings only for the auditSystem and auditUser configuration passes.

On an installed Windows operating system, run the sysprep /generalize /oobe command.

Even though the answer file is available in one of the implicit search paths, the Unattend.xml file is ignored because it does not contain a valid pass for the generalize configuration pass.

Additional Resources

See the following topics for more information about answer files and configuration passes:

Search Order	Location	Description