Applies ToWindows 7 Enterprise Windows 7 Home Basic Windows 7 Home Premium Windows 7 Professional Windows 7 Starter Windows 7 Ultimate
Not sure if this is the right fix? We’ve added this issue to our memory dump diagnostic which can confirm.
Symptoms
Consider the following scenario:
-
You have a computer that has an Intel H61 motherboard and 5 gigabytes (GB) of memory (4 GB + 1 GB).
-
You try to install a 32-bit version of Windows 7 on the computer.
In this scenario, the computer crashes during the startup process after the «copying files» stage. Therefore, the installation is not completed.
Notes If you remove the additional 1 GB of memory, the operating system installation can be completed successfully.
Cause
This issue occurs because the operating system does not successfully calculate the number of large pages that are needed.
Resolution
Hotfix information
A supported hotfix is available from Microsoft. However, this hotfix is intended to correct only the problem that is described in this article. Apply this hotfix only to systems that are experiencing the problem that is described in this article. This hotfix might receive additional testing. Therefore, if you are not severely affected by this problem, we recommend that you wait for the next software update that contains this hotfix.
If the hotfix is available for download, there is a «Hotfix download available» section at the top of this Knowledge Base article. If this section does not exist, contact Microsoft Customer Service and Support to obtain the hotfix.
Note If additional issues occur or if any troubleshooting is required, you might have to create a separate service request. The usual support costs will apply to additional support questions and issues that do not qualify for this specific hotfix. For a complete list of Microsoft Customer Service and Support telephone numbers or to create a separate service request, visit the following Microsoft website:
http://support.microsoft.com/contactus/?ws=supportNote The «Hotfix download available» form displays the languages for which the hotfix is available. If you do not see your language, it is because a hotfix is not available for that language.
Prerequisites
To apply this hotfix, you must be running one of the following operating systems:
-
Windows 7
-
Windows 7 with Service Pack 1 (SP1)
For more information about how to obtain a Windows 7 service pack or a Windows Server 2008 R2 service pack, click the following article number to view the article in the Microsoft Knowledge Base:
976932
Information about Service Pack 1 for Windows 7 and for Windows Server 2008 R2
Installation instructions
To install this hotfix, you can use one of the following methods:
-
To install this hotfix in the ordinary way, follow these steps:
-
Remove the 1 GB memory.
-
Install the operating system.
-
Install the hotfix after the system installation is completed.
-
Add the 1 GB memory back to the computer.
-
-
To convert this hotfix into .wim files, follow these steps:
-
-
Copy the contents of the Windows installation ISO image file to a folder. For example, copy the file to C:\WorkingDir.
-
Extract Hotfix_name.cab to a folder. For example, copy the file to C:\kb2550631.
-
Create a temporary mount directory. For example, create C:\temp\mount.
-
Mount Boot.wim by using a DISM command. To do this, open a Command Prompt window, type the following command, and then press Enter:
DISM /mount-wim /wimfile: C:\WorkingDir\sources\Boot.wim /index:2 /mountdir:C:\temp\mount
Note You may have several indexes. If there are two indexes, mount index 2. You can obtain a list of the indexes by running a DISM command. To do this, open a Command Prompt window, type the following command, and then press Enter:
DISM /get-wiminfo /wimfile: C:\WorkingDir\sources\Boot.wim
-
Add the package by using a DISM command. To do this, open a Command Prompt window, type the following command, and then press Enter:
DISM /image:C:\temp\mount /Add-Package /PackagePath:C:\kb2550631\Hotfixname.cab
-
Use a DISM command to unmount Boot.wim. To do this, open a Command Prompt window, type the following command, and then press Enter:
DISM /unmount-Wim /mountdir:C:\temp\mount /commit
-
Do the same operation to Install.wim.
Note You have to specify the Windows edition for which you have a product key. For example, if you use Windows 7 Ultimate, the index number for that product is needed. Additionally, you should specify the /index:number. Otherwise, this hotfix may not be in the index that you select to install.
-
Create the ISO file by using the Automated Installation Kit (AIK) for Windows 7 or the OEM Preinstallation Kit (OPK).
For more information about the AIK for Windows 7, visit the following Microsoft website:
The Windows OEM Preinstallation Kit (Windows OPK)
-
Registry information
To use the hotfix in this package, you do not have to make any changes to the registry.
Restart requirement
You must restart the computer after you apply this hotfix.
Hotfix replacement information
This hotfix does not replace a previously released hotfix.
File information
The global version of this hotfix installs files that have the attributes that are listed in the following tables. The dates and the times for these files are listed in Coordinated Universal Time (UTC). The dates and the times for these files on your local computer are displayed in your local time together with your current daylight saving time (DST) bias. Additionally, the dates and the times may change when you perform certain operations on the files.
Windows 7 file information notes
Important Windows 7 hotfixes and Windows Server 2008 R2 hotfixes are included in the same packages. However, hotfixes on the Hotfix Request page are listed under both operating systems. To request the hotfix package that applies to one or both operating systems, select the hotfix that is listed under «Windows 7/Windows Server 2008 R2» on the page. Always refer to the «Applies To» section in articles to determine the actual operating system to which each hotfix applies.
-
The files that apply to a specific product, SR_Level (RTM, SPn), and service branch (LDR, GDR) can be identified by examining the file version numbers as shown in the following table.
Version
Product
SR_Level
Service branch
6.1.760 0. 16xxx
Windows 7
RTM
GDR
6.1.760 0. 20xxx
Windows 7
RTM
LDR
6.1.760 1. 17xxx
Windows 7
SP1
GDR
6.1.760 1. 21xxx
Windows 7
SP1
LDR
-
The MANIFEST files (.manifest) and the MUM files (.mum) that are installed for each environment are listed separately in the «Additional file information for Windows 7» section. MUM and MANIFEST files, and the associated security catalog (.cat) files, are very important to maintaining the state of the updated components. The security catalog files, for which the attributes are not listed, are signed with a Microsoft digital signature.
For all supported x86-based versions of Windows 7
|
File name |
File version |
File size |
Date |
Time |
|---|---|---|---|---|
|
Ntoskrnl.exe |
6.1.7600.16818 |
11,176,832 |
20-May-2011 |
11:53 |
|
Ntoskrnl.exe |
6.1.7600.20970 |
11,132,800 |
20-May-2011 |
11:47 |
|
Ntoskrnl.exe |
6.1.7601.17619 |
11,118,464 |
20-May-2011 |
11:54 |
|
Ntoskrnl.exe |
6.1.7601.21731 |
11,118,976 |
20-May-2011 |
15:17 |
Status
Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the «Applies to» section.
More Information
For more information about software update terminology, click the following article number to view the article in the Microsoft Knowledge Base:
824684
Description of the standard terminology that is used to describe Microsoft software updates
Additional file information
Additional file information for Windows 7
Additional files for all supported x86-based versions of Windows 7
|
File name |
X86_0b8494dbca8a356b75092dec9edb979a_31bf3856ad364e35_6.1.7600.16818_none_a9a0976f4a919464.manifest |
|
File version |
Not applicable |
|
File size |
697 |
|
Date (UTC) |
21-May-2011 |
|
Time (UTC) |
00:11 |
|
File name |
X86_34bae623c55718e3629810d9212d6aa1_31bf3856ad364e35_6.1.7600.20970_none_3efccbf4bc6be043.manifest |
|
File version |
Not applicable |
|
File size |
697 |
|
Date (UTC) |
21-May-2011 |
|
Time (UTC) |
00:11 |
|
File name |
X86_a92a2d0d16c8e436c4ef4901c0eba088_31bf3856ad364e35_6.1.7601.21731_none_d110f2c5b1b8f384.manifest |
|
File version |
Not applicable |
|
File size |
697 |
|
Date (UTC) |
21-May-2011 |
|
Time (UTC) |
00:11 |
|
File name |
X86_aed5058efde001cf713d603860d9269f_31bf3856ad364e35_6.1.7601.17619_none_8dcdb604cb3161b6.manifest |
|
File version |
Not applicable |
|
File size |
697 |
|
Date (UTC) |
21-May-2011 |
|
Time (UTC) |
00:11 |
|
File name |
X86_e552cdc647ff1839d0fe779770be9639_31bf3856ad364e35_6.1.7600.16691_none_328fb89470173739.manifest |
|
File version |
Not applicable |
|
File size |
717 |
|
Date (UTC) |
21-May-2011 |
|
Time (UTC) |
00:11 |
|
File name |
X86_e8fbba93daf192ecaa483db1b3be6e89_31bf3856ad364e35_6.1.7600.20970_none_e1b9ab0faa9a8166.manifest |
|
File version |
Not applicable |
|
File size |
717 |
|
Date (UTC) |
21-May-2011 |
|
Time (UTC) |
00:11 |
|
File name |
X86_microsoft-windows-os-kernel_31bf3856ad364e35_6.1.7600.16818_none_6c557194153b220a.manifest |
|
File version |
Not applicable |
|
File size |
16,151 |
|
Date (UTC) |
20-May-2011 |
|
Time (UTC) |
12:32 |
|
File name |
X86_microsoft-windows-os-kernel_31bf3856ad364e35_6.1.7600.20970_none_6c962c872e909ec2.manifest |
|
File version |
Not applicable |
|
File size |
16,151 |
|
Date (UTC) |
20-May-2011 |
|
Time (UTC) |
12:44 |
|
File name |
X86_microsoft-windows-os-kernel_31bf3856ad364e35_6.1.7601.17619_none_6e3ccee41260a74d.manifest |
|
File version |
Not applicable |
|
File size |
16,151 |
|
Date (UTC) |
20-May-2011 |
|
Time (UTC) |
12:26 |
|
File name |
X86_microsoft-windows-os-kernel_31bf3856ad364e35_6.1.7601.21731_none_6ea8c9872b95b441.manifest |
|
File version |
Not applicable |
|
File size |
16,151 |
|
Date (UTC) |
20-May-2011 |
|
Time (UTC) |
15:58 |
|
File name |
X86_microsoft-windows-r..gistry-trustedtypes_31bf3856ad364e35_6.1.7600.16691_none_83c584548fc7607d.manifest |
|
File version |
Not applicable |
|
File size |
8,047 |
|
Date (UTC) |
20-Oct-2010 |
|
Time (UTC) |
05:25 |
|
File name |
X86_microsoft-windows-r..gistry-trustedtypes_31bf3856ad364e35_6.1.7600.20970_none_8463c479a8d5a95c.manifest |
|
File version |
Not applicable |
|
File size |
8,047 |
|
Date (UTC) |
20-May-2011 |
|
Time (UTC) |
12:33 |
Need more help?
Want more options?
Explore subscription benefits, browse training courses, learn how to secure your device, and more.
Пользователи Windows 7 и предыдущих версий ОС могут столкнуться с тем, что при запуске какой-либо программы, игры, установщика или любого другого .exe файла появляется ошибка «Не является приложением Win32», причем при появлении ошибки в x64 системах текст ошибки будет тем же — сообщат о том, что это не приложение Win32.
В этой инструкции подробно о возможных причинах появления этой ошибки и что делать в случае, если вы с ней столкнулись, чтобы запустить нужную программу. В Windows 10 эта же ошибка имеет другой вид: Невозможно запустить это приложение на вашем ПК.
- Причины ошибки Не является приложением Win32 и способы исправить проблему
- Видео инструкция
Причины ошибки «Не является приложением Win32» при запуске .exe файлов программ и варианты решения
Есть следующие основные причины, по которым появляется сообщение о том, что запускаемая программа не является приложением Win32:
- У вас установлена 32-бит Windows 7, а вы пробуете запустить файл .exe, предназначенный только для 64-бит Windows.
- Вы загрузили файл .exe для систем с процессорами ARM (часто бывает при скачивании компонентов Visual C++ Redistributable, так как для загрузки представлены могут быть представлены 3 разных файла, один из которых для ARM).
- Запускаемый файл .exe поврежден — например, он был восстановлен с помощью программ для восстановления данных, но его целостность была нарушена, либо причиной являются проблемы с жестким диском, флешкой или другим накопителем, где хранится этот файл.
- Файл изначально не был исполняемым файлом для Windows. Например, если вы просто переименуете любой файл, изменив его расширение на .exe, его не получится запустить и сообщит он именно об этой ошибке — программа не является приложением Win
- Редко — причина в том, что это файл очень старой программы, предназначенной для DOS или ранних версий Windows.
Исходя из этих основных причин, сделать для исправления ошибки «Не является приложением Win32» мы можем не слишком много:
- Если у вас система 32-бит (для того, чтобы посмотреть разрядность, нажмите правой кнопкой по «Мой компьютер» на рабочем столе или «Компьютер» в меню «Пуск» и откройте пункт «Свойства»), то либо найдите файл для 32-бит системы (он может обозначаться не только как 32-bit, но и как x86), либо откажитесь от запуска этого .exe, либо установите 64-бит Windows (придется с нуля устанавливать систему, просто «поменять 32-бит на x64» не получится).
- Если это файл какой-то старой программы, откройте его свойства и на вкладке «Совместимость» попробуйте включить режим совместимости с ранними версиями Windows.
- Не пытайтесь запустить файлы для ARM-процессоров на обычном компьютере, это не получится (кроме случая использования специальных эмуляторов).
- Простое переименование файлов и установка для них расширения .exe не приведет к возможности запуска такого файла. В некоторых установщиках вы можете встретить файлы вида setup.ex_ — как правило, это не файл .exe, а архив, его содержащий (можно попробовать распаковать любым архиватором, предварительно переименовав в .zip).
- Для случая поврежденных файлов решение — найти другой, «целый» файл для запуска. Исправление поврежденных файлов .exe — не то, что обычно получается сделать.
Видео инструкция
Пожалуй, это всё, что вы можете сделать в рассматриваемой ситуации. Если остаются вопросы — задавайте в комментариях, я постараюсь помочь в решении.
Вы уверены что только 32 битные перестали запускаться?
Ярлыки программ отношения к битности программы, на которую они ссылаются, не имеют.
Что происходит при запуске? Ошибка? Какая? Скриншот приложить было бы не плохо.
Посмотрите что прописано в реестре: HKLM\Software\WOW6432Node\Microsoft\Windows NT\CurrentVersion\Winlogon параметр Userinit. Должно быть «userinit.exe».
Обычно после обновлений такое часто бывает. Иногда помогает просто удалить проблемные обновления.
Запуск программы напрямую, а не через ярлык пробовали?
сделайте восстановление системы
Download Article
Download Article
- Causes of System 32 error:
- How to Prevent System 32 error
- Q&A
- Tips
|
|
|
System 32 error is the most common error which can halt the smooth work flow and make you feel dejected. Most of the people are still searching about “What is System 32 error?” why it happens? How does it affect? And what you can do to eliminate it? If you are also one of them then your search ends here, in this article I will let you know about the answers of all your questions regarding the System 32 error. I have looked up several forums, tech blogs and well renowned websites to collect the information.
System 32 is the one of the most important file hidden inside your computer which contains vital information required to function your computer properly. System 32 files generally located in the system drive C:\Windows\System32 in my PC (location on your computer can be different).
-
The most common reason of System 32 error is the corrupted registry which can lead to computer freeze. The most common affected files are Config.nt, autorun.inf and svchost.exe etc.
-
It can also be caused due to malwares which causes your computer to respond in undesired ways. Most of the malware enters your computer through spam mails and adware’s.
Advertisement
-
System 32 error can be triggered when you update your system files via internet. Some of the sites which promise to provide full version of software contain corrupted files or even are the Trojans which causes lethal damage by uploading virus on your computer.
-
When you replace or add any hardware then it may be possible that it’s not compatible to your existing computer setup which can create problem in the operating system. This can result in the System 32 error or you may hear different types of sounds during booting period of computer.
-
Any software update of your computer can also lead to unwanted changes in the registry which inhibits your computer to function properly.
Advertisement
-
Create a backup of your important data, so that if something wrong happens then you can restore all your important data from system backup. You have another option “system image”, by creating system image you can create backup of system settings, data, programs which are required to run your computer properly.
-
You can also use third party tools like Registry Cleaner offered by some of the well renowned companies like impcsupport. This tool can remove all registry error and also provide option to create backup of registry files.
-
Scan all your files on your computer, while downloading form the internet as they may contain suspicious element like virus, malware etc which can cause problem for your computer. Use a good antivirus program and update it regularly with latest virus definition. In my opinion you must use paid version as the free version antivirus has limited capability so it cannot provide full protection. The paid version offers maximum security and protects your computer from all harmful threats like virus, malware etc.
-
Before installing any software or updating any existing software it is always advised to check its compatibility with your computer.
Advertisement
Add New Question
-
Question
My PC doesn’t turn on and it writes system32 error on the screen?
If you have the original Disks or a recovery disk, you might be able to boot that way, or boot with F8 and use safe mode. You might need to reload Windows.
-
Question
I’m trying to install Windows 10 on my XP Pro desktop, and it says it’s not a win32 application. What can I do?
If you’re doing this on real hardware, check to ensure your hardware meets the hardware requirements, since Windows 10 is 14 years newer than Windows XP. If you’re using a newer XP computer that can run Windows 10, try booting from a Windows 10 installation USB or DVD and installing from there.
-
Question
What is a clean install?
A clean install is an install with any other stuff added before removed (otherwise it wouldn’t be «clean»).
See more answers
Ask a Question
200 characters left
Include your email address to get a message when this question is answered.
Submit
Advertisement
-
System 32 error is mainly caused due to corrupted registry, Virus, malware. For eliminating this problem it is always advised to create system backup regularly or you can use computer maintenance tools for getting permanent resolution.
Thanks for submitting a tip for review!
Advertisement
About This Article
Thanks to all authors for creating a page that has been read 103,947 times.