Skip to main content

WordPress: Upgrade error due to inconsistent file permission

While upgrading WordPress running on Microsoft Windows Server 2012 R2 from 4.6 to 4.7, I ran into error about file permission.

In short,
  1. TEMPORARILY add WRITE security permission to IIS_IUSRS local group for wordpress folder
  2. Run upgrade successfully, then
  3. Remove WRITE security permission of IIS_IUSRS local group from wordpress folder.
WordPress: Temporary security persmission settings to upgrade

Downloading update from https://downloads.wordpress.org/release/wordpress-4.7-new-bundled.zip
Unpacking the update…
The update cannot be installed because we will be unable to copy some files. This is usually due to inconsistent file permissions.: wp-admin/includes/update-core.php
Installation Failed

Check PHP error log: C:\Windows\Temps\PHP70x64_errors.log

[19-Dec-2016 12:04:29 UTC] PHP Warning:  copy(C:/wordpress/wp-admin/includes/update-core.php): failed to open stream: Permission denied in C:\wordpress\wp-admin\includes\class-wp-filesystem-direct.php on line 257

Downloading update from https://downloads.wordpress.org/release/wordpress-4.7-new-bundled.zip
Unpacking the update…
Verifying the unpacked files…
Preparing to install the latest version…
Enabling Maintenance mode…
Copying the required files…
Disabling Maintenance mode…
Could not copy file.: index.php
Installation Failed
WordPress.com

Popular posts from this blog

MSSQL: Fix error 'Consistency validation for SQL Server registry keys'

While installing Microsof SQL Server 2012, I ran into the following error. "The SQL Server registry keys from a prior installation cannot be modified. To continue, see SQL Server Setup documentation about how to fix registry keys." How to fix Replace the D:\x64\FixSqlRegistryKey_x86.exe file with the original file from the ENU\SQLFULL_ENU.iso file downloading from Microsoft Download Center. This ISO file is 4.2GB. So you can click FixSqlRegistryKey_x86.exe to download this file only. After replacing that file, press Re-run to check. All rules are passed.

Powershell: Check Bad Logon

get-aduser -Filter {BadLogonCount -ne 0} -properties * | select SamAccountName,BadLogonCount,BadPasswordTime,BadPwdCount,@{name='badPasswordTimeDT'; expression={[datetime]::fromFileTime($_.badPasswordTime)}} | sort BadPasswordTime | FT

GIMP - GNU Image Manipulation Program

Download GIMP for Windows, MacOS, and Linux.