System File Checker gives an administrator the ability to scan all protected files to verify their versions. If System File Checker discovers that a protected file has been overwritten, it retrieves the correct version of the file from the cache folder (%Systemroot% System32 Dllcache) or the Windows installation source files, and then replaces the incorrect file.
Apr 10, 2018. Pro License Cracking; ✓ Cara Install Ulang Windows Xp Sp3 Menggunakan Flash Disk Tidak Terdeteksi; ✓ Script For Moving Files Based On.
System File Checker also checks and repopulates the cache folder. You must be logged on as an administrator or as a member of the Administrators group to run System File Checker. If the cache folder becomes damaged or unusable, you can use the sfc /scannow, the sfc /scanonce, or the sfc /scanboot commands to repair its contents. Back to the top System File Checker Tool Syntax Sfc /Scannow /Scanonce /Scanboot /Revert /Purgecache /Cachesize=x. /Scannow: Scans all protected system files immediately and replaces incorrect versions with correct Microsoft versions. This command may require access to the Windows installation source files. /Scanonce: Scans all protected system files one time when you restart your computer.
This command may require access to the Windows installation source files when you restart the computer. The SfcScan DWORD value is set to 2 in the following registry key when you run this command: HKEYLOCALMACHINE SOFTWARE Microsoft Windows NT CurrentVersion Winlogon.
/Scanboot: Scans all protected system files every time you start your computer. This command may require access to the Windows installation source files every time you start your computer. The SfcScan DWORD value is set to 1 in the following registry key when you run this command: HKEYLOCALMACHINE SOFTWARE Microsoft Windows NT CurrentVersion Winlogon. /Revert: Returns scan to the default setting (do not scan protected files when you start the computer).The default cache size is not reset when you run this command. This command is equivalent to the /Enable switch in Windows 2000. /Purgecache: Purges the file cache and scans all protected system files immediately. This command may require access to the Windows installation source files.
/Cachesize=x: Sets the file cache size to x megabytes (MB). The default size of the cache is 50 MB. This command requires you to restart the computer, and then run the /purgecache command to adjust the size of the on-disk cache. How the WFP feature works The WFP feature provides protection for system files using two mechanisms. The first mechanism runs in the background. This protection is triggered after WFP receives a directory change notification for a file in a protected directory. After WFP receives this notification, WFP determines which file was changed.
If the file is protected, WFP looks up the file signature in a catalog file to determine if the new file is the correct version. If the file is not the correct version, WFP replaces the new file with the file from the cache folder (if it is in the cache folder) or from the installation source. WFP searches for the correct file in the following locations, in this order:. The cache folder (by default,%systemroot% system32 dllcache). The network install path, if the system was installed using network install. The Windows CD-ROM, if the system was installed from CD-ROM.
If WFP finds the file in the cache folder or if the installation source is automatically located, WFP silently replaces the file and logs an event that resembles the following in the System log. Windows File Protection Files that are required for Windows to run properly have been replaced by unrecognized versions. To maintain system stability, Windows must restore the original versions of these files. The network location from which these files should be copied, server share, is not available. Contact your system administrator or insert product CD-ROM now. Note If an administrator is not logged on, WFP cannot display either of these dialog boxes. In this situation, WFP displays the dialog box after an administrator logs on.
WFP may wait for an administrator to log on in the following scenarios:. The SFCShowProgress registry entry is missing or is set to 1, and the server is set to scan every time that the computer starts. In this situation, WFP waits for a console logon. Therefore, the RPC server does not start until the scan is performed. The computer has no protection during this time.
Note You can still map network drives, use system files, and use Terminal Services to log on to the server. WFP does not consider these operations as a console logon, and keeps waiting indefinitely. WFP has to restore a file from a network share. This situation may occur if the file is not present in the Dllcache folder or if the file is corrupted. In this situation, WFP may not have the correct credentials to access the share from the network-based installation media.
The second protection mechanism that is provided by the WFP feature is the System File Checker (Sfc.exe) tool. At the end of GUI-mode Setup, the System File Checker tool scans all the protected files to make sure that they are not modified by programs that were installed by using an unattended installation. The System File Checker tool also checks all the catalog files that are used to track correct file versions.
If any of the catalog files are missing or damaged, WFP renames the affected catalog file and retrieves a cached version of that file from the cache folder. If a cached copy of the catalog file is not available in the cache folder, the WFP feature requests the appropriate media to retrieve a new copy of the catalog file. The System File Checker tool gives an administrator the ability to scan all the protected files to verify their versions. The System File Checker tool also checks and repopulates the cache folder (by default,%SystemRoot% System32 Dllcache). If the cache folder becomes damaged or unusable, you can use either the sfc /scanonce command or the sfc /scanboot command at a command prompt to repair the contents of the folder. The SfcScan value in the following registry key has three possible settings. HKEYLOCALMACHINE SOFTWARE Microsoft Windows NT CurrentVersion Winlogon The settings for the SfcScan value are:.
0x0 = do not scan protected files after restart. (Default value). 0x1 = scan all protected files after every restart (set if sfc /scanboot is run). 0x2 = scan all protected files one time after a restart (set if sfc /scanonce is run). By default, all system files are cached in the cache folder, and the default size of the cache is 400 MB. Because of disk space considerations, it may not be desirable to maintain cached versions of all system files in the cache folder.
To change the size of the cache, change the setting of the SFCQuota value in the following registry key. HKEYLOCALMACHINE Software Microsoft Windows NT CurrentVersion Winlogon WFP stores verified file versions in the Dllcache folder on the hard disk. The number of cached files is determined by the setting of the SFCQuota value (the default size is 0xFFFFFFFF, or 400 MB).
The administrator can make the setting for the SFCQuota value as large or small as needed. Note that if you set the SFCQuota value to 0xFFFFFFFF, the WFP feature caches all protected system files (approximately 2,700 files). There are two cases in which the cache folder may not contain copies of all protected files, regardless of the SFCQuota value:. Not enough disk space. Under Windows XP, WFP stops populating the Dllcache folder when less than (600 MB + maximum size of the page file) of space is available on the hard disk.
Under Windows 2000, WFP stops populating the Dllcache folder when less than 600 MB of space is available on the hard disk. Network Install. When Windows 2000 or Windows XP is installed over the network, files in the i386 lang directory are not populated in the Dllcache folder.
Additionally, all drivers in the Driver.cab file are protected, but they are not populated in the Dllcache folder. WFP can restore these files from the Driver.cab file directly without prompting the user for the source media. However, running the sfc /scannow command does populate the files from the Driver.cab file into the Dllcache folder. If WFP detects a file change and the affected file is not in the cache folder, WFP examines the version of the changed file that the operating system is currently using. If the file that is currently in use is the correct version, WFP copies that version of the file to the cache folder. If the file that is currently in use is not the correct version, or if the file is not cached in the cache folder, WFP tries to locate the installation source.
If WFP cannot find the installation source, WFP prompts an administrator to insert the appropriate media to replace the file or the cached file version. The SFCDllCacheDir value (REGEXPANDSZ) in the following registry key specifies the location of the Dllcache folder. Kalo mungkin da yang belum tau. Berikut ini Tips untuk membuat Windows anda sedikit lebih bergegas kinerjanya. Mendisable Service Windows yg tidak diperlukan. Karena windows ditujukan untuk berbagai user dan tugas, maka windows membuat service yg sebenarnya tidak tidak terlalu diperlukan.
Service2 berikut ini seringkali memakan resouce yg tidak sedikit, dengan mendisable (me-non-aktif-kan) maka komputer kita bisa mendapatkan sedikit boost karenanya. Install ulang sistem operasi Windows? Repair atau gagal repair Windows? Atau gagal install ulang Windows? Demikian masalah yang sering muncul, entah anda pengguna Windows XP, Windows Vista, Windows 7 atau bahkan OS yang lain. Mulai artikel ini sampai beberapa artikel ke depan saya akan membahas mengenai instalasi windows dalam berbagai versi.
Ada kalanya ketika repair windows tidak berhasil, disinilah kita harus melakukan instal ulang. Pertanyaannya adalah apa itu install ulang? Install ulang Windows adalah sebuah usaha untuk memasukkan kembali semua files-file system operasi Windows kedalam sebuah path/dirve tertentu pada hard disk sehinggan komputer dapat beroperasi kembali secara normal.
Ini dilakukan ketika windows mengalami kerusakan atau sebagian filenya hilang. Dalam install ulang semua versi windows didalamnya ada beberapa pilihan yang dapat ditempuh; 1.
Clean installation. Dalam bahasa pasar install total.
Dalam proses ini kita menghapus semua data/file dalam drive (biasanya C: ) yang merupakan tempat system operasi. Penghapusan tadi dilakukan baik dengan men-delete partisi system lalu membuatnya kembali atau hanya dengan cara mem-format partisi hard disk untuk drive system operasi. Ini bias dilakukan jika semua data penting pada drive system sebelimnya telah diamankan dengan backup. Apa jeleknya?
Jeleknya adalah lama dan ada kemungkinan ada data yang lupa diamankan jadi hilang. Bagusnya adalah komputer akan segar kembali jika sebelumnya ada virus komputer maka dipastikan akan bersih kembali sesudah instalasi selesai. Install tanpa format hard disk system, artinya kita hanya menimpa semua file system operasinya tetapi program aplikasi lain tetap utuh. Bagusnya adalah semuat setting dan aplikasi dalam komputer akan kembali seperti sebelumnya. Jekenya adalah jika ada worm, virus ataupun malware maka penyakit tersebut akan tetap tinggal dalam komputer.
Dalam proses install biasanya ada pilihan no changes sebagai identitas pilihan instalasi ini. Sebenarnya masih ada lagi satu yaitu pilihan repair yaitu hanya memperbaiki file-file system operasi yang rusak atau hilang. Ini juga tidak menyelesaikan masalah virus tetapi waktunya singkat disbanding dua langkah sebelumnya. Lalu mengapa system operasi windows diinstall ulang? Karena terserang virus dan sudah tidak ada pilihan lain alias sudah stress gara-gara virus.
Karena system operasi sudah terlalu banyak file sampah yang tidak tertangani oleh software pembersih file sampah. Harap dimengerti bahwa software pembersih file sampah jika tidak tepat kadang justru menimbulkan masalah pada computer misalnya pada registry editor.
Karena system operasi sudah sedemikian lambat dan meng-uninstall sebagian program aplikasi ternyata tidak menyelesaikan masalah. Karena konfik antara program aplikasi maupun dengan system operasi sehingga komputer malas bekerja atau bahkan mogok kerja. Dan masih banyak lagi alas an lain mengenai hal ini. CATATAN: jangan takut melakukan install ulang windows asal perhatikan langkah-langkahnya dengan benar. Mengatasi gagal install ulang windows Dan mengapa sering terjadi gagal install ulang windows? Bagaimana mengatasi kegagalan install ulang windows? Beberapa hal yang sering menjadi penyebabnya.
Ada 5 perangkat keras yang secara langsung terlibat dalam proses install ulang window yaitu Mrocessor, Main Memory, Hard disk, CD/DVD ROM, CD installer dan 3 yang terakhir yang paling bertanggung jawab untuk kegagalan proses instalasi. Inilah solusinya; 1. Kegagalan pada CD installer. Biasanya CD installer yang sudah tua dan banyak goresan akan susah dibaca oleh CD ROM. Dari sinilah awalnya.
Oleh karena itu pastikan CD installer masih sangat layak untuk digunakan. Jika CD installer rusak maka akan muncul beberapa kali pesan can’t copy file. Sebenarnya pesan ini bisa diabaikan dengan pilihan Skip tetapi kemungkinan besar nantinya ada kegagalan tertentu ketika windows sudah berjalan di desktop. CD/DVD ROM rusak, kabur optiknya. Jika optik CD/DVD ROM kabur alias berdebu, maka dia tidak bisa membaca CD dengan tepat dan jika ini terjadi maka proses akan menjadi sangat lambat selanjutnya akan sangat lambat atau terhenti lalu muncul peringatan kegagalan. Peringatan paling keras dari kegagalan ini adalah Blue screen of death. Pastikan kabel CD/DVD ROM terpasang dengan tepat, kalau perlu siapkan CD/DVD ROM cadangan.
Kesalahan menulis pada hard disk. Ada kalanya terjadi kegagalan mengcopy file-file kedalam hard disk sehingga proses install gagal. Permasalahan listrik tidak stabil bias mengganggu proses ini. Penyebab lain adalah kabel data hard disk longgar atau tidak tepat ketika akan memulai meng-copy file kedalamnya langsung timbul kegagalan. Biasanya hard disk yang sudah tua dan tidak stabil lagi juga menyebabkan hal ini, walaupun hard disk masih terdeteksi di BIOS.
Perbaiki kedudukan kabel data dan siapkan hard disk cadangan. Jika semua jalan keluar diatas sudah anda tempuh pasti proses install sudah berhasil.
Nah sekarang saya piker sudah sangat jelas bagi kita apa, mengapa dan bagaimana mengatasi install ulang windows. Corrupt.Exe menjadi Icon Windows Media Center. Vocal Remover (Winamp) 1.03 So you want to impress your friends with your singing skills, but they only listen to boring old top 40 songs–and your brand-new karaoke machine is broken. There’s still hope.
AnalogX Vocal Remover works on the same principles that hardware removers do: In most instances vocals are equally mixed in both channels and can be identified and removed by simply changing the phase on one channel by 180 degrees. Although this won’t remove vocals in all instances, it works in many cases and can sometimes be used to remove bass or breakbeat sections, which is great for sampling. Depending on the effects used on the vocals, sometimes the reverb or ambience remains. Vocal Remover requires a stereo sound stream and supports either 16-bit or 32-bit data types.
To use the Winamp Vocal Remover, you must already have Winamp installed as well as a stereo sound stream, and it supports only 16-bit data types. Operating system: Windows 98/Me/2000/XP/NT Download.
System File Checker gives an administrator the ability to scan all protected files to verify their versions. If System File Checker discovers that a protected file has been overwritten, it retrieves the correct version of the file from the cache folder (%Systemroot% System32 Dllcache) or the Windows installation source files, and then replaces the incorrect file. System File Checker also checks and repopulates the cache folder.
You must be logged on as an administrator or as a member of the Administrators group to run System File Checker. If the cache folder becomes damaged or unusable, you can use the sfc /scannow, the sfc /scanonce, or the sfc /scanboot commands to repair its contents. Back to the top System File Checker Tool Syntax Sfc /Scannow /Scanonce /Scanboot /Revert /Purgecache /Cachesize=x. /Scannow: Scans all protected system files immediately and replaces incorrect versions with correct Microsoft versions.
This command may require access to the Windows installation source files. /Scanonce: Scans all protected system files one time when you restart your computer.
This command may require access to the Windows installation source files when you restart the computer. The SfcScan DWORD value is set to 2 in the following registry key when you run this command: HKEYLOCALMACHINE SOFTWARE Microsoft Windows NT CurrentVersion Winlogon. /Scanboot: Scans all protected system files every time you start your computer. This command may require access to the Windows installation source files every time you start your computer.
The SfcScan DWORD value is set to 1 in the following registry key when you run this command: HKEYLOCALMACHINE SOFTWARE Microsoft Windows NT CurrentVersion Winlogon. /Revert: Returns scan to the default setting (do not scan protected files when you start the computer).The default cache size is not reset when you run this command.
This command is equivalent to the /Enable switch in Windows 2000. /Purgecache: Purges the file cache and scans all protected system files immediately. This command may require access to the Windows installation source files.
/Cachesize=x: Sets the file cache size to x megabytes (MB). The default size of the cache is 50 MB. This command requires you to restart the computer, and then run the /purgecache command to adjust the size of the on-disk cache. How the WFP feature works The WFP feature provides protection for system files using two mechanisms. The first mechanism runs in the background. This protection is triggered after WFP receives a directory change notification for a file in a protected directory.
After WFP receives this notification, WFP determines which file was changed. If the file is protected, WFP looks up the file signature in a catalog file to determine if the new file is the correct version. If the file is not the correct version, WFP replaces the new file with the file from the cache folder (if it is in the cache folder) or from the installation source. WFP searches for the correct file in the following locations, in this order:. The cache folder (by default,%systemroot% system32 dllcache). The network install path, if the system was installed using network install. The Windows CD-ROM, if the system was installed from CD-ROM.
If WFP finds the file in the cache folder or if the installation source is automatically located, WFP silently replaces the file and logs an event that resembles the following in the System log. Windows File Protection Files that are required for Windows to run properly have been replaced by unrecognized versions. To maintain system stability, Windows must restore the original versions of these files. The network location from which these files should be copied, server share, is not available. Contact your system administrator or insert product CD-ROM now. Note If an administrator is not logged on, WFP cannot display either of these dialog boxes. In this situation, WFP displays the dialog box after an administrator logs on.
WFP may wait for an administrator to log on in the following scenarios:. The SFCShowProgress registry entry is missing or is set to 1, and the server is set to scan every time that the computer starts.
In this situation, WFP waits for a console logon. Therefore, the RPC server does not start until the scan is performed. The computer has no protection during this time. Note You can still map network drives, use system files, and use Terminal Services to log on to the server. WFP does not consider these operations as a console logon, and keeps waiting indefinitely. WFP has to restore a file from a network share. This situation may occur if the file is not present in the Dllcache folder or if the file is corrupted.
In this situation, WFP may not have the correct credentials to access the share from the network-based installation media. The second protection mechanism that is provided by the WFP feature is the System File Checker (Sfc.exe) tool. At the end of GUI-mode Setup, the System File Checker tool scans all the protected files to make sure that they are not modified by programs that were installed by using an unattended installation. The System File Checker tool also checks all the catalog files that are used to track correct file versions.
If any of the catalog files are missing or damaged, WFP renames the affected catalog file and retrieves a cached version of that file from the cache folder. If a cached copy of the catalog file is not available in the cache folder, the WFP feature requests the appropriate media to retrieve a new copy of the catalog file. The System File Checker tool gives an administrator the ability to scan all the protected files to verify their versions.
The System File Checker tool also checks and repopulates the cache folder (by default,%SystemRoot% System32 Dllcache). If the cache folder becomes damaged or unusable, you can use either the sfc /scanonce command or the sfc /scanboot command at a command prompt to repair the contents of the folder. The SfcScan value in the following registry key has three possible settings. HKEYLOCALMACHINE SOFTWARE Microsoft Windows NT CurrentVersion Winlogon The settings for the SfcScan value are:.
0x0 = do not scan protected files after restart. (Default value). 0x1 = scan all protected files after every restart (set if sfc /scanboot is run). 0x2 = scan all protected files one time after a restart (set if sfc /scanonce is run).
By default, all system files are cached in the cache folder, and the default size of the cache is 400 MB. Because of disk space considerations, it may not be desirable to maintain cached versions of all system files in the cache folder. To change the size of the cache, change the setting of the SFCQuota value in the following registry key. HKEYLOCALMACHINE Software Microsoft Windows NT CurrentVersion Winlogon WFP stores verified file versions in the Dllcache folder on the hard disk. The number of cached files is determined by the setting of the SFCQuota value (the default size is 0xFFFFFFFF, or 400 MB).
The administrator can make the setting for the SFCQuota value as large or small as needed. Note that if you set the SFCQuota value to 0xFFFFFFFF, the WFP feature caches all protected system files (approximately 2,700 files). There are two cases in which the cache folder may not contain copies of all protected files, regardless of the SFCQuota value:. Not enough disk space. Under Windows XP, WFP stops populating the Dllcache folder when less than (600 MB + maximum size of the page file) of space is available on the hard disk. Under Windows 2000, WFP stops populating the Dllcache folder when less than 600 MB of space is available on the hard disk. Network Install.
When Windows 2000 or Windows XP is installed over the network, files in the i386 lang directory are not populated in the Dllcache folder. Additionally, all drivers in the Driver.cab file are protected, but they are not populated in the Dllcache folder. WFP can restore these files from the Driver.cab file directly without prompting the user for the source media. However, running the sfc /scannow command does populate the files from the Driver.cab file into the Dllcache folder. If WFP detects a file change and the affected file is not in the cache folder, WFP examines the version of the changed file that the operating system is currently using. If the file that is currently in use is the correct version, WFP copies that version of the file to the cache folder. If the file that is currently in use is not the correct version, or if the file is not cached in the cache folder, WFP tries to locate the installation source.
If WFP cannot find the installation source, WFP prompts an administrator to insert the appropriate media to replace the file or the cached file version. The SFCDllCacheDir value (REGEXPANDSZ) in the following registry key specifies the location of the Dllcache folder. Kalo mungkin da yang belum tau.
Berikut ini Tips untuk membuat Windows anda sedikit lebih bergegas kinerjanya. Mendisable Service Windows yg tidak diperlukan.
Karena windows ditujukan untuk berbagai user dan tugas, maka windows membuat service yg sebenarnya tidak tidak terlalu diperlukan. Service2 berikut ini seringkali memakan resouce yg tidak sedikit, dengan mendisable (me-non-aktif-kan) maka komputer kita bisa mendapatkan sedikit boost karenanya. Install ulang sistem operasi Windows? Repair atau gagal repair Windows? Atau gagal install ulang Windows? Demikian masalah yang sering muncul, entah anda pengguna Windows XP, Windows Vista, Windows 7 atau bahkan OS yang lain.
Mulai artikel ini sampai beberapa artikel ke depan saya akan membahas mengenai instalasi windows dalam berbagai versi. Ada kalanya ketika repair windows tidak berhasil, disinilah kita harus melakukan instal ulang. Pertanyaannya adalah apa itu install ulang? Install ulang Windows adalah sebuah usaha untuk memasukkan kembali semua files-file system operasi Windows kedalam sebuah path/dirve tertentu pada hard disk sehinggan komputer dapat beroperasi kembali secara normal. Ini dilakukan ketika windows mengalami kerusakan atau sebagian filenya hilang.
Dalam install ulang semua versi windows didalamnya ada beberapa pilihan yang dapat ditempuh; 1. Clean installation. Dalam bahasa pasar install total.
Dalam proses ini kita menghapus semua data/file dalam drive (biasanya C: ) yang merupakan tempat system operasi. Penghapusan tadi dilakukan baik dengan men-delete partisi system lalu membuatnya kembali atau hanya dengan cara mem-format partisi hard disk untuk drive system operasi. Ini bias dilakukan jika semua data penting pada drive system sebelimnya telah diamankan dengan backup. Apa jeleknya? Jeleknya adalah lama dan ada kemungkinan ada data yang lupa diamankan jadi hilang.
Bagusnya adalah komputer akan segar kembali jika sebelumnya ada virus komputer maka dipastikan akan bersih kembali sesudah instalasi selesai. Install tanpa format hard disk system, artinya kita hanya menimpa semua file system operasinya tetapi program aplikasi lain tetap utuh. Bagusnya adalah semuat setting dan aplikasi dalam komputer akan kembali seperti sebelumnya. Jekenya adalah jika ada worm, virus ataupun malware maka penyakit tersebut akan tetap tinggal dalam komputer. Dalam proses install biasanya ada pilihan no changes sebagai identitas pilihan instalasi ini. Sebenarnya masih ada lagi satu yaitu pilihan repair yaitu hanya memperbaiki file-file system operasi yang rusak atau hilang. Ini juga tidak menyelesaikan masalah virus tetapi waktunya singkat disbanding dua langkah sebelumnya.
Lalu mengapa system operasi windows diinstall ulang? Karena terserang virus dan sudah tidak ada pilihan lain alias sudah stress gara-gara virus. Karena system operasi sudah terlalu banyak file sampah yang tidak tertangani oleh software pembersih file sampah. Harap dimengerti bahwa software pembersih file sampah jika tidak tepat kadang justru menimbulkan masalah pada computer misalnya pada registry editor. Karena system operasi sudah sedemikian lambat dan meng-uninstall sebagian program aplikasi ternyata tidak menyelesaikan masalah. Karena konfik antara program aplikasi maupun dengan system operasi sehingga komputer malas bekerja atau bahkan mogok kerja. Dan masih banyak lagi alas an lain mengenai hal ini.
CATATAN: jangan takut melakukan install ulang windows asal perhatikan langkah-langkahnya dengan benar. Mengatasi gagal install ulang windows Dan mengapa sering terjadi gagal install ulang windows? Bagaimana mengatasi kegagalan install ulang windows?
Beberapa hal yang sering menjadi penyebabnya. Ada 5 perangkat keras yang secara langsung terlibat dalam proses install ulang window yaitu Mrocessor, Main Memory, Hard disk, CD/DVD ROM, CD installer dan 3 yang terakhir yang paling bertanggung jawab untuk kegagalan proses instalasi.
Inilah solusinya; 1. Kegagalan pada CD installer.
Biasanya CD installer yang sudah tua dan banyak goresan akan susah dibaca oleh CD ROM. Dari sinilah awalnya. Oleh karena itu pastikan CD installer masih sangat layak untuk digunakan. Jika CD installer rusak maka akan muncul beberapa kali pesan can’t copy file. Sebenarnya pesan ini bisa diabaikan dengan pilihan Skip tetapi kemungkinan besar nantinya ada kegagalan tertentu ketika windows sudah berjalan di desktop.
CD/DVD ROM rusak, kabur optiknya. Jika optik CD/DVD ROM kabur alias berdebu, maka dia tidak bisa membaca CD dengan tepat dan jika ini terjadi maka proses akan menjadi sangat lambat selanjutnya akan sangat lambat atau terhenti lalu muncul peringatan kegagalan. Peringatan paling keras dari kegagalan ini adalah Blue screen of death. Pastikan kabel CD/DVD ROM terpasang dengan tepat, kalau perlu siapkan CD/DVD ROM cadangan. Kesalahan menulis pada hard disk. Ada kalanya terjadi kegagalan mengcopy file-file kedalam hard disk sehingga proses install gagal.
Permasalahan listrik tidak stabil bias mengganggu proses ini. Penyebab lain adalah kabel data hard disk longgar atau tidak tepat ketika akan memulai meng-copy file kedalamnya langsung timbul kegagalan. Biasanya hard disk yang sudah tua dan tidak stabil lagi juga menyebabkan hal ini, walaupun hard disk masih terdeteksi di BIOS. Perbaiki kedudukan kabel data dan siapkan hard disk cadangan. Jika semua jalan keluar diatas sudah anda tempuh pasti proses install sudah berhasil.
Nah sekarang saya piker sudah sangat jelas bagi kita apa, mengapa dan bagaimana mengatasi install ulang windows. Corrupt.Exe menjadi Icon Windows Media Center.