How the Windows Imaging Component Works

This topic contains the following sections:

Discovery and Arbitration

Before an image can be decoded, an appropriate codec must be found that can decode that image format. In most systems, because the supported image formats are hard-coded, no discovery process is required. Because the Windows Imaging Component (WIC) platform is extensible, it’s necessary to be able to identify the format of an image and match it with an appropriate codec.

To support run-time discovery, each image format must have an identifying pattern that can be used to identify the appropriate decoder for that format. (It is strongly recommended that, for new file formats, you use a GUID for the identifying pattern, because it is guaranteed to be unique.) The identifying pattern must be embedded in each image file that conforms to that image format. Each decoder has a registry entry that specifies the identifying pattern or patterns of the image formats it can decode. When an application needs to open an image, it requests a decoder from WIC. WIC looks up the available decoders in the registry, and checks each registry entry for an identifying pattern that matches the pattern embedded in the image file. For more information on decoder registry entries, see Encoder-Specific Registry Entries

When WIC finds a single decoder that matches the identifying pattern in the image, it creates an instance of the decoder and passes the image file to it. If WIC finds more than one match, it invokes a method called QueryCapability on each matching decoder to arbitrate among them and find the best match. For more information, see the QueryCapabilities section in the Implementing IWICBitmapDecoder.

Decoding

After the appropriate decoder has been selected and instantiated, the application talks directly to the decoder. The decoder has several responsibilities, which it implements through various interfaces. These services can be classified as:

• Container-level services
• Frame-level services
• Metadata enumeration services
• Native decoder transforms
• Progress notifications and cancellation support
• Raw processing services

Container-level services include retrieving the top-level thumbnail (if supported), preview, color contexts, palette (if applicable), and container format, as well as providing access to the individual image frames within the container. (Some containers contain only a single frame while others, such as Tagged Image File Format (TIFF), can contain multiple frames.) This set of services also includes providing information about the decoder itself, and its capabilities with respect to a specific image file.

Individual frames have their own thumbnails, and may also have their own color contexts, palettes, and other properties, which are exposed at the frame level. The most important operation performed at the frame level, though, is the actual decoding of the image bits for that frame.

WIC provides metadata readers for the most common metadata formats (IFD, EXIF, IPTC, XMP, APP0, APP1, and other formats), and also supports extensibility for third-party metadata formats. This frees the codec of the responsibility for parsing metadata. However, the codec is responsible for enumerating the metadata blocks and requesting a metadata reader for each block. WIC performs discovery for metadata handlers the same way it does for codecs, based on a pattern in the block header matching a pattern in the metadata handler’s registry entry. For more information, see the Encoder-Specific Registry Entries

Decoders are not required to natively support transform operations, but doing so enables significant performance optimizations that provide a better end-user experience. For example, an application can create a pipeline of various transforms (scaling, cropping, rotation, and pixel format conversion) to perform on an image before the image is rendered. For more information on transform pipelines, see IWICBitmapSource. After creating a transform pipeline, the application requests the final transform in the pipeline to produce the bitmap that results from applying all the transforms to the image source. At that point, if the decoder itself is able to perform transform operations, WIC asks which of the requested transforms it can perform. Any requested transforms the decoder cannot perform will be performed by WIC on the decoded image before returning it to the caller. This optimized transform pipeline provides better performance than performing each transform sequentially in memory, particularly when some or all of the transforms can be accomplished during the decoding process.

Progress notifications and cancellation support enable an application to request progress notifications for lengthy operations, and also enable the application to give the user an opportunity to cancel an operation that is taking too long. This is important because if a user cannot cancel an operation, he or she may feel the process has hung, and try to cancel it by closing the application.

These interfaces are described in detail in the section on Implementing a WIC-Enabled Decoder.

Raw processing services include adjusting camera settings, such as exposure, contrast, and sharpening, or changing the color space before processing the raw bits.

Encoding

Like decoders, encoders have responsibilities that they implement through interfaces. The services that encoders provide are complementary to the services provided by decoders, except they write out image data rather than reading it. Encoders also provide services in the following categories:

• Container-level services
• Frame-level services
• Metadata enumeration and update services
• Progress notification and cancellation support

Container-level services for an encoder include setting the top-level thumbnail (if supported), preview, and palette (if applicable), and iterating through the individual image frames so they can be serialized into the container.

Frame-level services for an encoder mirror those for the decoder, except that they write out the image data, thumbnail, and any associated palette or other component, rather than reading them.

Also, metadata enumeration services for an encoder include iterating through the metadata blocks to be written, and invoking the appropriate metadata writers to serialize the metadata to disk.

These interfaces are described in detail in the section on Implementing a WIC-Enabled Encoder.

The Lifetime of a Codec

A WIC codec is instantiated to handle a single image, and usually has a short lifetime. It’s created when an image is loaded and is released when the image is closed. An application may use a large number of codecs simultaneously with overlapping lifetimes (think of scrolling through a directory containing hundreds of images), and multiple applications may be doing this at the same time.

Although some codecs have a lifetime that is scoped to the lifetime of the process in which they live, this is not the case with WIC codecs. The WindowsВ Vista Photo Gallery, Windows Explorer, and Photo Viewer, as well as numerous other applications, are built on WIC and will be using your codec to display images and thumbnails. If the lifetime of your codec were scoped to the lifetime of the process, every time an image or thumbnail was displayed in the WindowsВ Vista Explorer, the codec instantiated to decode that image would remain in memory until the next time the user restarted his or her computer. If your codec is never unloaded, its resources are, in effect, «leaked» because they can’t be used by any other component in the system.

How to WIC-enabled a Codec

1. Implement a container-level decoder class and a frame-level decoder class that exposes the required WIC interfaces for decoding images and iterating through blocks of metadata. This enables all WIC-based applications to interact with your codec the same way they interact with standard image formats.
2. Implement a container-level encoder class and a frame-level encoder class that exposes the required WIC interfaces for encoding images and serializing blocks of metadata into an image file.
3. If your container format is not based on a TIFF or JPEG container, you may need to write metadata handlers for the common metadata formats (EXIF, XMP). However, if you use a TIFF-based or JPEG-based container format, this is not necessary because you can delegate to the system-provided metadata handlers.
4. Embed a unique identifying pattern (we recommend a GUID) in all your image files. This enables your image format to be matched against your codec during the discovery. If you are writing a WIC wrapper for an existing image format, you must find a pattern of bits that the encoder always writes into its image files that’s unique to that image format, and use this as the identifying pattern.)
5. Register your codec at installation time. This enables your codec to be discovered at run time by matching the identifying pattern in the registry with the pattern embedded in the image file.
6. As of WindowsВ 7, WIC requires that codecs be of COM apartment type «Both». This means that you must do the appropriate locking to handle cross-apartment callers and callers in multi-threaded scenarios. For more information, see the next section on multi-threaded apartment support.
7. Support for 64-bit platforms: For WindowsВ 7, WIC will require that third-party WIC codecs be delivered as both 32-bit and 64-bit native binaries. Further, the 32-bit form must install and run on 64-bit systems, and the third party WindowsВ 7 codec installer must install both the 32-bit and 64-bit binaries on 64-bit systems.

Multi-Threaded Apartment Support in WIC

Objects within a Multi-Threaded Apartment (MTA) may be called concurrently by any number of threads within the MTA. This allows for better performance on multi-core systems and certain server scenarios. In addition, WIC codecs in an MTA can call other objects in the MTA without the marshalling cost associated with calling between threads in different STA apartments. In WindowsВ 7, all in-box WIC codecs have been updated to support MTAs, including JPEG, TIFF, PNG, GIF, ICO, and BMP. It is highly recommended that third-party codecs be written to support MTAs. Third-party codecs that do not to support MTAs cause significant performance costs in multi-threaded applications because of marshaling. Enabling MTA support requires proper synchronization to be implemented in the third-party codec. Exact implementation of these synchronization techniques is beyond the scope of this paper. For more information on synchronizing COM objects, see Understanding and Using COM Threading Models.

Windows Imaging Component Overview

The Windows Imaging Component (WIC) provides an extensible framework for working with images and image metadata. WIC makes it possible for independent software vendors (ISVs) and independent hardware vendors (IHVs) to develop their own image codecs and get the same platform support as standard image formats (for example, TIFF, JPEG, PNG, GIF, BMP, and HDPhoto). A single, consistent set of interfaces is used for all image processing, regardless of image format, so any application using the WIC gets automatic support for new image formats as soon as the codec is installed. The extensible metadata framework makes it possible for applications to read and write their own proprietary metadata directly to image files, so the metadata never gets lost or separated from the image.

This topic includes the following sections.

Windows Imaging Component Features

The primary features of WIC are:

• Enables application developers to perform image processing operations on any image format through a single, consistent set of common interfaces, without requiring prior knowledge of specific image formats.
• Provides an extensible «plug and play» architecture for image codecs, pixel formats, and metadata, with automatic run-time discovery of new formats.
• Supports reading and writing of arbitrary metadata in image files, with the ability to preserve unrecognized metadata during editing.
• Preserves high bit depth image data, up to 32 bits per channel, throughout the image processing pipeline.
• Provides built-in support for most popular image formats, pixel formats, and metadata schemas.

Native Codecs

WIC includes several built-in codecs. The following standard codecs are provided with the platform.

You must install windows imaging component

Профиль | Отправить PM | Цитировать

1\AppData\Local\Temp\Microsoft .NET Framework 4 Client Profile Setup_4.0.30319\Windows6.1-KB958488-v6001-x86.msu) failed with 0x80240017 — (null).
Exe (L:\510470f95f86b58631ce\SetupUtility.exe) succeeded and requires reboot.
Exe Log File: dd_SetupUtility.txt
MSI (C:\Users\899A

1\AppData\Local\Temp\Microsoft .NET Framework 4 Client Profile Setup_4.0.30319\netfx_Core_x86.msi) Installation failed. Msi Log: Microsoft .NET Framework 4 Client Profile Setup_20120922_221421879-MSI_netfx_Core_x86.msi.txt
Final Result: Installation failed with error code: (0x80070643), «В процессе установки произошла неисправимая ошибка. » (Elapsed time: 0 00:00:32).

Это сообщение посчитали полезным следующие участники:

Сообщения: 10692
Благодарности: 2884

Конфигурация компьютера
Материнская плата: MSI H61M-P21 (MS-7680) (B3.0)
HDD: WDC Caviar Green WD10EARS-22Y5B1 ATA Device 1Т (1000 Gb), WDC Caviar Blue WD10EZEX-08M2NA0 ATA Device 1Т (1000 Gb)
Звук: VIA VT1708S VIA High Definition Audio
CD/DVD: ATAPI iHAS122 ATA Device
ОС: Microsoft Windows 7 Home Basic x86, Microsoft Windows 10 Home x64 .
Прочее: Multi Flash Reader USB Device, Logitech HD Webcam C310

Покажите раздел реестра HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\services\ BITS

——-
Будь джентльменом, если есть удача. А нет удачи, джентльменов нет . Нажми .

Если же вы забыли свой пароль на форуме, то воспользуйтесь данной ссылкой для восстановления пароля.

Сообщения: 51908
Благодарности: 14931

Конфигурация компьютера
Материнская плата: ASUS P8Z77-V LE PLUS
HDD: Samsung SSD 850 PRO 256 Гб, WD Green WD20EZRX 2 Тб
Звук: Realtek ALC889 HD Audio
CD/DVD: ASUS DRW-24B5ST
ОС: Windows 8.1 Pro x64
Прочее: корпус: Fractal Design Define R4

Это сообщение посчитали полезным следующие участники:

Упс, ошибочка. Надо переустановит SP3.Сначала удалите его https://support.microsoft.com/ru-ru/kb/950249, а потом установите вновь через Центр обновления. Но установка с обновлением, без потери данных есть и в ХР. Не пойму, что вам не даёт это сделать. Вставьте дистрибутив в привод, откройте его, запустите файл setup.exe и выберите установка и следом обновление. »

Здравствуйте,
Переустановил SP3 — не помогло.
Переустановил OS Windows — опять не помогло. (!)

опять выдает вот это:

=== Verbose logging started: 16.05.2016 0:38:36 Build type: SHIP UNICODE 3.01.4001.5512 Calling process: C:\d83e71aaf7cf193357\Setup.exe ===
MSI (c) (A0:B8) [00:38:36:914]: Resetting cached policy values
MSI (c) (A0:B8) [00:38:36:914]: Machine policy value ‘Debug’ is 0
MSI (c) (A0:B8) [00:38:36:914]: ******* RunEngine:
******* Product: C:\d83e71aaf7cf193357\netfx_Core_x86.msi
******* Action:
******* CommandLine: **********
MSI (c) (A0:B8) [00:38:36:924]: Client-side and UI is none or basic: Running entire install on the server.
MSI (c) (A0:B8) [00:38:36:964]: Grabbed execution mutex.
MSI (c) (A0:B8) [00:38:39:538]: Cloaking enabled.
MSI (c) (A0:B8) [00:38:39:538]: Attempting to enable all disabled priveleges before calling Install on Server
MSI (c) (A0:B8) [00:38:39:598]: Incrementing counter to disable shutdown. Counter after increment: 0
MSI (s) (60:20) [00:38:39:798]: Grabbed execution mutex.
MSI (s) (60:EC) [00:38:39:808]: Resetting cached policy values
MSI (s) (60:EC) [00:38:39:808]: Machine policy value ‘Debug’ is 0
MSI (s) (60:EC) [00:38:39:808]: ******* RunEngine:
******* Product: C:\d83e71aaf7cf193357\netfx_Core_x86.msi
******* Action:
******* CommandLine: **********
MSI (s) (60:EC) [00:38:39:898]: Machine policy value ‘DisableUserInstalls’ is 0
MSI (s) (60:EC) [00:38:40:158]: File will have security applied from OpCode.
MSI (s) (60:EC) [00:38:40:329]: SOFTWARE RESTRICTION POLICY: Verifying package —> ‘C:\d83e71aaf7cf193357\netfx_Core_x86.msi’ against software restriction policy
MSI (s) (60:EC) [00:38:40:329]: SOFTWARE RESTRICTION POLICY: C:\d83e71aaf7cf193357\netfx_Core_x86.msi has a digital signature
MSI (s) (60:EC) [00:38:42:572]: SOFTWARE RESTRICTION POLICY: C:\d83e71aaf7cf193357\netfx_Core_x86.msi is permitted to run at the ‘unrestricted’ authorization level.
MSI (s) (60:EC) [00:38:42:592]: End dialog not enabled
MSI (s) (60:EC) [00:38:42:592]: Original package ==> C:\d83e71aaf7cf193357\netfx_Core_x86.msi
MSI (s) (60:EC) [00:38:42:592]: Package we’re running from ==> C:\Windows\Installer\fe30f.msi
MSI (s) (60:EC) [00:38:42:882]: APPCOMPAT: looking for appcompat database entry with ProductCode ‘<3c3901c5-3455-3e0a-a214-0b093a5070a6>‘.
MSI (s) (60:EC) [00:38:42:892]: APPCOMPAT: no matching ProductCode found in database.
MSI (s) (60:EC) [00:38:42:972]: MSCOREE not loaded loading copy from system32
MSI (s) (60:EC) [00:38:43:443]: Machine policy value ‘TransformsSecure’ is 0
MSI (s) (60:EC) [00:38:43:443]: User policy value ‘TransformsAtSource’ is 0
MSI (s) (60:EC) [00:38:43:473]: Machine policy value ‘DisablePatch’ is 0
MSI (s) (60:EC) [00:38:43:473]: Machine policy value ‘AllowLockdownPatch’ is 0
MSI (s) (60:EC) [00:38:43:473]: Machine policy value ‘DisableLUAPatching’ is 0
MSI (s) (60:EC) [00:38:43:473]: Machine policy value ‘DisableFlyWeightPatching’ is 0
MSI (s) (60:EC) [00:38:43:483]: APPCOMPAT: looking for appcompat database entry with ProductCode ‘<3c3901c5-3455-3e0a-a214-0b093a5070a6>‘.
MSI (s) (60:EC) [00:38:43:483]: APPCOMPAT: no matching ProductCode found in database.
MSI (s) (60:EC) [00:38:43:483]: Transforms are not secure.
MSI (s) (60:EC) [00:38:43:483]: Note: 1: 2205 2: 3: Control
MSI (s) (60:EC) [00:38:43:483]: Command Line: EXTUI=1 CURRENTDIRECTORY=C:\d83e71aaf7cf193357 CLIENTUILEVEL=3 CLIENTPROCESSID=672
MSI (s) (60:EC) [00:38:43:483]: PROPERTY CHANGE: Adding PackageCode property. Its value is ‘‘.
MSI (s) (60:EC) [00:38:43:483]: Product Code passed to Engine.Initialize: »
MSI (s) (60:EC) [00:38:43:483]: Product Code from property table before transforms: ‘<3c3901c5-3455-3e0a-a214-0b093a5070a6>‘
MSI (s) (60:EC) [00:38:43:483]: Product Code from property table after transforms: ‘<3c3901c5-3455-3e0a-a214-0b093a5070a6>‘
MSI (s) (60:EC) [00:38:43:483]: Product not registered: beginning first-time install
MSI (s) (60:EC) [00:38:43:483]: PROPERTY CHANGE: Adding ProductState property. Its value is ‘-1’.
MSI (s) (60:EC) [00:38:43:483]: Entering CMsiConfigurationManager::SetLastUsedSource.
MSI (s) (60:EC) [00:38:43:483]: User policy value ‘SearchOrder’ is ‘nmu’
MSI (s) (60:EC) [00:38:43:483]: Adding new sources is allowed.
MSI (s) (60:EC) [00:38:43:483]: PROPERTY CHANGE: Adding PackagecodeChanging property. Its value is ‘1’.
MSI (s) (60:EC) [00:38:43:483]: Package name extracted from package path: ‘netfx_Core_x86.msi’
MSI (s) (60:EC) [00:38:43:483]: Package to be registered: ‘netfx_Core_x86.msi’
MSI (s) (60:EC) [00:38:43:483]: Note: 1: 2729
MSI (s) (60:EC) [00:38:43:493]: Note: 1: 2729
MSI (s) (60:EC) [00:38:43:503]: Note: 1: 2729
MSI (s) (60:EC) [00:38:43:503]: Note: 1: 2729
MSI (s) (60:EC) [00:38:43:513]: Note: 1: 2729
MSI (s) (60:EC) [00:38:43:513]: Note: 1: 2729
MSI (s) (60:EC) [00:38:43:513]: Note: 1: 2729
MSI (s) (60:EC) [00:38:43:523]: Note: 1: 2729
MSI (s) (60:EC) [00:38:43:523]: Note: 1: 2729
MSI (s) (60:EC) [00:38:43:533]: Note: 1: 2729
MSI (s) (60:EC) [00:38:43:533]: Note: 1: 2729
MSI (s) (60:EC) [00:38:43:533]: Note: 1: 2729
MSI (s) (60:EC) [00:38:43:533]: Note: 1: 2729
MSI (s) (60:EC) [00:38:43:543]: Note: 1: 2729
MSI (s) (60:EC) [00:38:43:543]: Note: 1: 2729
MSI (s) (60:EC) [00:38:43:543]: Note: 1: 2729
MSI (s) (60:EC) [00:38:43:553]: Note: 1: 2262 2: AdminProperties 3: -2147287038
MSI (s) (60:EC) [00:38:43:553]: Machine policy value ‘DisableMsi’ is 0
MSI (s) (60:EC) [00:38:43:553]: Machine policy value ‘AlwaysInstallElevated’ is 0
MSI (s) (60:EC) [00:38:43:553]: User policy value ‘AlwaysInstallElevated’ is 0
MSI (s) (60:EC) [00:38:43:553]: Product installation will be elevated because user is admin and product is being installed per-machine.
MSI (s) (60:EC) [00:38:43:553]: Running product ‘<3c3901c5-3455-3e0a-a214-0b093a5070a6>‘ with elevated privileges: Product is assigned.
MSI (s) (60:EC) [00:38:43:553]: PROPERTY CHANGE: Adding EXTUI property. Its value is ‘1’.
MSI (s) (60:EC) [00:38:43:553]: PROPERTY CHANGE: Adding CURRENTDIRECTORY property. Its value is ‘C:\d83e71aaf7cf193357’.
MSI (s) (60:EC) [00:38:43:553]: PROPERTY CHANGE: Adding CLIENTUILEVEL property. Its value is ‘3’.
MSI (s) (60:EC) [00:38:43:553]: PROPERTY CHANGE: Adding CLIENTPROCESSID property. Its value is ‘672’.
MSI (s) (60:EC) [00:38:43:553]: TRANSFORMS property is now:
MSI (s) (60:EC) [00:38:43:553]: PROPERTY CHANGE: Adding VersionDatabase property. Its value is ‘300’.
MSI (s) (60:EC) [00:38:43:573]: SHELL32::SHGetFolderPath returned: C:\Documents and Settings\Administrator\Application Data
MSI (s) (60:EC) [00:38:43:573]: SHELL32::SHGetFolderPath returned: C:\Documents and Settings\Administrator\Favorites
MSI (s) (60:EC) [00:38:43:573]: SHELL32::SHGetFolderPath returned: C:\Documents and Settings\Administrator\NetHood
MSI (s) (60:EC) [00:38:43:573]: SHELL32::SHGetFolderPath returned: C:\Documents and Settings\Administrator\My Documents
MSI (s) (60:EC) [00:38:43:583]: SHELL32::SHGetFolderPath returned: C:\Documents and Settings\Administrator\PrintHood
MSI (s) (60:EC) [00:38:43:583]: SHELL32::SHGetFolderPath returned: C:\Documents and Settings\Administrator\Recent
MSI (s) (60:EC) [00:38:43:583]: SHELL32::SHGetFolderPath returned: C:\Documents and Settings\Administrator\SendTo
MSI (s) (60:EC) [00:38:43:593]: SHELL32::SHGetFolderPath returned: C:\Documents and Settings\Administrator\Templates
MSI (s) (60:EC) [00:38:43:593]: SHELL32::SHGetFolderPath returned: C:\Documents and Settings\All Users\Application Data
MSI (s) (60:EC) [00:38:43:593]: SHELL32::SHGetFolderPath returned: C:\Documents and Settings\Administrator\Local Settings\Application Data
MSI (s) (60:EC) [00:38:43:593]: SHELL32::SHGetFolderPath returned: C:\Documents and Settings\Administrator\My Documents\My Pictures
MSI (s) (60:EC) [00:38:43:623]: SHELL32::SHGetFolderPath returned: C:\Documents and Settings\All Users\Start Menu\Programs\Administrative Tools
MSI (s) (60:EC) [00:38:43:643]: SHELL32::SHGetFolderPath returned: C:\Documents and Settings\All Users\Start Menu\Programs\Startup
MSI (s) (60:EC) [00:38:43:643]: SHELL32::SHGetFolderPath returned: C:\Documents and Settings\All Users\Start Menu\Programs
MSI (s) (60:EC) [00:38:43:653]: SHELL32::SHGetFolderPath returned: C:\Documents and Settings\All Users\Start Menu
MSI (s) (60:EC) [00:38:43:653]: SHELL32::SHGetFolderPath returned: C:\Documents and Settings\All Users\Desktop
MSI (s) (60:EC) [00:38:43:653]: SHELL32::SHGetFolderPath returned: C:\Documents and Settings\Administrator\Start Menu\Programs\Administrative Tools
MSI (s) (60:EC) [00:38:43:663]: SHELL32::SHGetFolderPath returned: C:\Documents and Settings\Administrator\Start Menu\Programs\Startup
MSI (s) (60:EC) [00:38:43:674]: SHELL32::SHGetFolderPath returned: C:\Documents and Settings\Administrator\Start Menu\Programs
MSI (s) (60:EC) [00:38:43:674]: SHELL32::SHGetFolderPath returned: C:\Documents and Settings\Administrator\Start Menu
MSI (s) (60:EC) [00:38:43:674]: SHELL32::SHGetFolderPath returned: C:\Documents and Settings\Administrator\Desktop
MSI (s) (60:EC) [00:38:43:674]: SHELL32::SHGetFolderPath returned: C:\Documents and Settings\All Users\Templates
MSI (s) (60:EC) [00:38:43:684]: SHELL32::SHGetFolderPath returned: C:\Windows\Fonts
MSI (s) (60:EC) [00:38:43:684]: Note: 1: 2898 2: MS Sans Serif 3: Arial 4: 0 5: 16
MSI (s) (60:EC) [00:38:43:704]: PROPERTY CHANGE: Adding Privileged property. Its value is ‘1’.
MSI (s) (60:EC) [00:38:43:704]: Note: 1: 1402 2: HKEY_CURRENT_USER\Software\Microsoft\MS Setup (ACME)\User Info 3: 2
MSI (s) (60:EC) [00:38:43:704]: PROPERTY CHANGE: Adding USERNAME property. Its value is ‘Administrator’.
MSI (s) (60:EC) [00:38:43:704]: Note: 1: 1402 2: HKEY_CURRENT_USER\Software\Microsoft\MS Setup (ACME)\User Info 3: 2
MSI (s) (60:EC) [00:38:43:704]: PROPERTY CHANGE: Adding COMPANYNAME property. Its value is ‘OEM’.
MSI (s) (60:EC) [00:38:43:704]: PROPERTY CHANGE: Adding DATABASE property. Its value is ‘C:\Windows\Installer\fe30f.msi’.
MSI (s) (60:EC) [00:38:43:704]: PROPERTY CHANGE: Adding OriginalDatabase property. Its value is ‘C:\d83e71aaf7cf193357\netfx_Core_x86.msi’.
MSI (s) (60:EC) [00:38:43:704]: Note: 1: 2205 2: 3: PatchPackage
MSI (s) (60:EC) [00:38:43:704]: Machine policy value ‘DisableRollback’ is 0
MSI (s) (60:EC) [00:38:43:704]: User policy value ‘DisableRollback’ is 0
MSI (s) (60:EC) [00:38:43:704]: PROPERTY CHANGE: Adding UILevel property. Its value is ‘2’.
MSI (s) (60:EC) [00:38:43:704]: PROPERTY CHANGE: Adding MsiUISourceResOnly property. Its value is ‘1’.
=== Logging started: 16.05.2016 0:38:43 ===
MSI (s) (60:EC) [00:38:43:704]: PROPERTY CHANGE: Adding ACTION property. Its value is ‘INSTALL’.
MSI (s) (60:EC) [00:38:43:704]: Doing action: INSTALL
MSI (s) (60:EC) [00:38:43:704]: Note: 1: 2205 2: 3: ActionText
MSI (s) (60:EC) [00:38:43:734]: Running ExecuteSequence
MSI (s) (60:EC) [00:38:43:734]: Skipping action: DDSE_CA_Uninstall_InstallExecuteSequenceStarts_x86 (condition is false)
MSI (s) (60:EC) [00:38:43:734]: Doing action: FindRelatedProducts
MSI (s) (60:EC) [00:38:43:734]: Note: 1: 2205 2: 3: ActionText
Action start 0:38:43: INSTALL.
Action start 0:38:43: FindRelatedProducts.
MSI (s) (60:EC) [00:38:43:754]: Skipping action: CA_BlockOlderVersionInstall (condition is false)
MSI (s) (60:EC) [00:38:43:754]: Doing action: AppSearch
MSI (s) (60:EC) [00:38:43:754]: Note: 1: 2205 2: 3: ActionText
Action ended 0:38:43: FindRelatedProducts. Return value 1.
Action start 0:38:43: AppSearch.
MSI (s) (60:EC) [00:38:43:814]: Note: 1: 1325 2: windowscodecs.dll
MSI (s) (60:EC) [00:38:43:814]: Note: 1: 1402 2: HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\.NETFramework\v4.0\Core\SBSDisabled 3: 2
MSI (s) (60:EC) [00:38:43:824]: Note: 1: 1402 2: HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\.NETFramework\v4.0\Core\SBSDisabled 3: 2
MSI (s) (60:EC) [00:38:43:824]: Note: 1: 1402 2: HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\NET Framework Setup\OS Integration 3: 2
MSI (s) (60:EC) [00:38:43:824]: Doing action: CA_ASPPlusVersionCmd_x86
MSI (s) (60:EC) [00:38:43:824]: Note: 1: 2205 2: 3: ActionText
Action ended 0:38:43: AppSearch. Return value 1.
MSI (s) (60:EC) [00:38:43:874]: PROPERTY CHANGE: Adding ASPPlusVersion property. Its value is ‘4.0.30319’.
Action start 0:38:43: CA_ASPPlusVersionCmd_x86.
MSI (s) (60:EC) [00:38:43:884]: Skipping action: CA_Block_NetFx40_Core_SXSDisabled_Install (condition is false)
MSI (s) (60:EC) [00:38:43:884]: Skipping action: CA_Block_NetFx40_Core_SXSDisabled_Uninstall (condition is false)
MSI (s) (60:EC) [00:38:43:884]: Skipping action: CA_Block_NetFx40_On_Windows2008ServerCore (condition is false)
MSI (s) (60:EC) [00:38:43:884]: Doing action: CA_Block_WIC_NotPresent_x86
MSI (s) (60:EC) [00:38:43:884]: Note: 1: 2205 2: 3: ActionText
Action ended 0:38:43: CA_ASPPlusVersionCmd_x86. Return value 1.
Action start 0:38:43: CA_Block_WIC_NotPresent_x86.
MSI (s) (60:EC) [00:38:43:904]: Product: Microsoft .NET Framework 4 Client Profile — You must install the 32-bit Windows Imaging Component (WIC) before you run Setup. Please visit http://go.microsoft.com/fwlink/?Link. 43&clcid=0x409 to install WIC, and then rerun Setup.

You must install the 32-bit Windows Imaging Component (WIC) before you run Setup. Please visit http://go.microsoft.com/fwlink/?Link. 43&clcid=0x409 to install WIC, and then rerun Setup.
Action ended 0:38:43: CA_Block_WIC_NotPresent_x86. Return value 3.
Action ended 0:38:43: INSTALL. Return value 3.
Property(S): UpgradeCode = <10e35dd9-8269-3f1e-97f4-99f0da3c2cec>
Property(S): WPFFontCache_x86_ID = WPFFontCache_v0400_x86
Property(S): WPFFontCacheServiceName_x86 = Windows Presentation Foundation Font Cache 4.0.0.0
Property(S): WPFFontCacheServiceDescription_x86 = Optimizes performance of Windows Presentation Foundation (WPF) applications by caching commonly used font data. WPF applications will start this service if it is not already running. It can be disabled, though doing so will degrade the performance of WPF applications.
Property(S): ASPPlusVersion = 4.0.30319
Property(S): VersionNT = 501
Property(S): Manufacturer = Microsoft Corporation
Property(S): ProductCode = <3c3901c5-3455-3e0a-a214-0b093a5070a6>
Property(S): ProductLanguage = 0
Property(S): ProductName = Microsoft .NET Framework 4 Client Profile
Property(S): ProductVersion = 4.0.30319
Property(S): ProductShortName = .NET Framework 4 Client Profile
Property(S): LocProductName = Microsoft .NET Framework 4 Client Profile
Property(S): ProductEdition = core
Property(S): ProductFamily = netfx
Property(S): ProductImage = net
Property(S): ProductCPU = x86
Property(S): ALLUSERS = 1
Property(S): INSTALLLEVEL = 1
Property(S): FXAssemblyVersion = 4.0.0.0
Property(S): VSAssemblyVersion = 10.0.0.0
Property(S): ReqCLRVersion = v4.0.30319
Property(S): WPFRegistryKey = Windows Presentation Foundation
Property(S): WPFStaticVersion = 4.0
Property(S): RTM_ProductVersion = 4.0.30319
Property(S): netfxpri1 = 1
Property(S): ARPNOMODIFY = 1
Property(S): ARPNOREPAIR = 1
Property(S): ARPSYSTEMCOMPONENT = 1
Property(S): URTVersion = v4.0.30319
Property(S): URTBuildNum = 30319
Property(S): ARPSIZE = 39732
Property(S): ARPREADME = http://go.microsoft.com/fwlink/?LinkId=164156
Property(S): ARPURLINFOABOUT = http://go.microsoft.com/fwlink/?LinkId=164164
Property(S): ARPURLUPDATEINFO = http://go.microsoft.com/fwlink/?LinkId=164165
Property(S): DirectoryTable100_x86 = DirectoryTable
Property(S): NgenServiceFiles = mscorsvc.dll;mscorsvw.exe;ngen.exe
Property(S): NgenExclusionList = aspnet_isapi.dll;aspnet_perf.h;aspnet_perf.ini;aspnet_perf2.ini;aspnet_regiis.exe;aspnet_wp.exe;c1xx .dll;c2.dll;CORPerfMonExt.dll;cscomp.dll;InstallPersistSqlState.sql;InstallSqlState.sql;InstallSqlSt ateTemplate.sql;PerfCounter.dll;SmartNav.htm;SmartNav.js;SmartNavIE5.js;System.Windows.Forms.tlb;Uni nstallPersistSqlState.sql;UninstallSqlStateTemplate.sql
Property(S): SharedComponentVersion = 4.0.31106.0
Property(S): MAINTMODE = IdentityCacheDir
Property(S): SecureCustomProperties = NEWERVERSIONDETECTED;UPGRADENETFXCORE40
Property(S): PackageCode =
Property(S): ProductState = -1
Property(S): PackagecodeChanging = 1
Property(S): EXTUI = 1
Property(S): CURRENTDIRECTORY = C:\d83e71aaf7cf193357
Property(S): CLIENTUILEVEL = 3
Property(S): CLIENTPROCESSID = 672
Property(S): VersionDatabase = 300
Property(S): VersionMsi = 3.01
Property(S): WindowsBuild = 2600
Property(S): ServicePackLevel = 3
Property(S): ServicePackLevelMinor = 0
Property(S): MsiNTProductType = 1
Property(S): WindowsFolder = C:\Windows\
Property(S): WindowsVolume = C:\
Property(S): SystemFolder = C:\Windows\system32\
Property(S): System16Folder = C:\Windows\system\
Property(S): RemoteAdminTS = 1
Property(S): TempFolder = C:\DOCUME

1\Temp\
Property(S): ProgramFilesFolder = C:\Program Files\
Property(S): CommonFilesFolder = C:\Program Files\Common Files\
Property(S): AppDataFolder = C:\Documents and Settings\Administrator\Application Data\
Property(S): FavoritesFolder = C:\Documents and Settings\Administrator\Favorites\
Property(S): NetHoodFolder = C:\Documents and Settings\Administrator\NetHood\
Property(S): PersonalFolder = C:\Documents and Settings\Administrator\My Documents\
Property(S): PrintHoodFolder = C:\Documents and Settings\Administrator\PrintHood\
Property(S): RecentFolder = C:\Documents and Settings\Administrator\Recent\
Property(S): SendToFolder = C:\Documents and Settings\Administrator\SendTo\
Property(S): TemplateFolder = C:\Documents and Settings\All Users\Templates\
Property(S): CommonAppDataFolder = C:\Documents and Settings\All Users\Application Data\
Property(S): LocalAppDataFolder = C:\Documents and Settings\Administrator\Local Settings\Application Data\
Property(S): MyPicturesFolder = C:\Documents and Settings\Administrator\My Documents\My Pictures\
Property(S): AdminToolsFolder = C:\Documents and Settings\All Users\Start Menu\Programs\Administrative Tools\
Property(S): StartupFolder = C:\Documents and Settings\All Users\Start Menu\Programs\Startup\
Property(S): ProgramMenuFolder = C:\Documents and Settings\All Users\Start Menu\Programs\
Property(S): StartMenuFolder = C:\Documents and Settings\All Users\Start Menu\
Property(S): DesktopFolder = C:\Documents and Settings\All Users\Desktop\
Property(S): FontsFolder = C:\Windows\Fonts\
Property(S): GPTSupport = 1
Property(S): OLEAdvtSupport = 1
Property(S): ShellAdvtSupport = 1
Property(S): Intel = 15
Property(S): PhysicalMemory = 320
Property(S): VirtualMemory = 790
Property(S): AdminUser = 1
Property(S): LogonUser = Administrator
Property(S): UserSID = S-1-5-21-1644491937-152049171-1343024091-500
Property(S): UserLanguageID = 1049
Property(S): ComputerName = AQYPC61AFWEZVFZ
Property(S): SystemLanguageID = 1049
Property(S): ScreenX = 1024
Property(S): ScreenY = 768
Property(S): CaptionHeight = 26
Property(S): BorderTop = 1
Property(S): BorderSide = 1
Property(S): TextHeight = 16
Property(S): ColorBits = 16
Property(S): TTCSupport = 1
Property(S): Time = 0:38:44
Property(S): Date = 16.05.2016
Property(S): MsiNetAssemblySupport = 2.0.50727.3053
Property(S): MsiWin32AssemblySupport = 5.1.2600.5512
Property(S): RedirectedDllSupport = 2
Property(S): Privileged = 1
Property(S): USERNAME = Administrator
Property(S): COMPANYNAME = OEM
Property(S): DATABASE = C:\Windows\Installer\fe30f.msi
Property(S): OriginalDatabase = C:\d83e71aaf7cf193357\netfx_Core_x86.msi
Property(S): UILevel = 2
Property(S): MsiUISourceResOnly = 1
Property(S): ACTION = INSTALL
MSI (s) (60:EC) [00:38:44:154]: Note: 1: 1708
MSI (s) (60:EC) [00:38:44:164]: Product: Microsoft .NET Framework 4 Client Profile — Installation failed.

MSI (s) (60:EC) [00:38:44:194]: Cleaning up uninstalled install packages, if any exist
MSI (s) (60:EC) [00:38:44:194]: MainEngineThread is returning 1603
=== Logging stopped: 16.05.2016 0:38:44 ===
MSI (c) (A0:B8) [00:38:44:304]: Decrementing counter to disable shutdown. If counter >= 0, shutdown will be denied. Counter after decrement: -1
MSI (c) (A0:B8) [00:38:44:314]: MainEngineThread is returning 1603
=== Verbose logging stopped: 16.05.2016 0:38:44 ===