Title: wordpress 4.6.1
Last modified: September 7, 2016

---

# wordpress 4.6.1

 *  [gjensen](https://wordpress.org/support/users/gjensen/)
 * (@gjensen)
 * [9 years, 9 months ago](https://wordpress.org/support/topic/wordpress-4-6-1/)
 * doe sit work with wordpress 4.6.1?

Viewing 6 replies - 1 through 6 (of 6 total)

 *  [bluebearmedia](https://wordpress.org/support/users/bluebearmedia/)
 * (@bluebearmedia)
 * [9 years, 9 months ago](https://wordpress.org/support/topic/wordpress-4-6-1/#post-8156326)
 * So far so good on about a dozen or so of my client sites!
 *  [willnev](https://wordpress.org/support/users/willnev/)
 * (@willnev)
 * [9 years, 9 months ago](https://wordpress.org/support/topic/wordpress-4-6-1/#post-8156383)
 * When running a scan a few mins ago, I received the following message under the“
   New Issues” section.
 * Unknown WordPress core version: 4.6.1
 * I’m assuming that because the latest version of WordPress was just released, 
   this message is nothing to be concerned about correct?
 * Thanks for making such a great product!
 *  [Acies](https://wordpress.org/support/users/acies/)
 * (@acies)
 * [9 years, 9 months ago](https://wordpress.org/support/topic/wordpress-4-6-1/#post-8156413)
 * The rest of the message after running a scan should answer the question:
 * “The core files scan will not be run because this version of WordPress is not
   currently indexed by Wordfence. This may be due to using a prerelease version
   or because the servers are still indexing a new release. If you are using an 
   official WordPress release, this issue will automatically dismiss once the version
   is indexed and another scan is run.”
 * It’s unfortunate that Wordfence did not index the new version before release 
   as usual. My inbox is now filling with Wordfence Alerts, and clients are calling
   with questions because some of them also receive the alerts.
 *  [mophilly](https://wordpress.org/support/users/mophilly/)
 * (@mophilly)
 * [9 years, 9 months ago](https://wordpress.org/support/topic/wordpress-4-6-1/#post-8156630)
 * I am getting the error message on four of our sites now.
 * The bottom line is to get the WordFence up to date so we can move forward. Is
   there an ETA for a resolution? (the technical resolution, not the political one)
    -  This reply was modified 9 years, 9 months ago by [mophilly](https://wordpress.org/support/users/mophilly/).
 *  [webado](https://wordpress.org/support/users/webado/)
 * (@webado)
 * [9 years, 9 months ago](https://wordpress.org/support/topic/wordpress-4-6-1/#post-8156889)
 * I got an email from WF also saying: Unknown WordPress core version: 4.6.1
 * I suppose it will get sorted soon. It looks like this WP version came fast with
   no pre-announcement.
    I had no opportunity to see what the changes may have been
   so soon after 4.6 .
 *  [jmetro](https://wordpress.org/support/users/jmetro/)
 * (@jmetro)
 * [9 years, 9 months ago](https://wordpress.org/support/topic/wordpress-4-6-1/#post-8157024)
 * Thank you Acies, I too got this unusual message.
    Came here to check and now 
   feel much better. Solution: wait

Viewing 6 replies - 1 through 6 (of 6 total)

The topic ‘wordpress 4.6.1’ is closed to new replies.

 * ![](https://ps.w.org/wordfence/assets/icon.svg?rev=2070865)
 * [Wordfence Security - Firewall, Malware Scan, and Login Security](https://wordpress.org/plugins/wordfence/)
 * [Frequently Asked Questions](https://wordpress.org/plugins/wordfence/#faq)
 * [Support Threads](https://wordpress.org/support/plugin/wordfence/)
 * [Active Topics](https://wordpress.org/support/plugin/wordfence/active/)
 * [Unresolved Topics](https://wordpress.org/support/plugin/wordfence/unresolved/)
 * [Reviews](https://wordpress.org/support/plugin/wordfence/reviews/)

## Tags

 * [wordpress 4.6.1](https://wordpress.org/support/topic-tag/wordpress-4-6-1/)

 * 6 replies
 * 7 participants
 * Last reply from: [jmetro](https://wordpress.org/support/users/jmetro/)
 * Last activity: [9 years, 9 months ago](https://wordpress.org/support/topic/wordpress-4-6-1/#post-8157024)
 * Status: not resolved