Blogger’s Cyberbullying Mission Tiresome, Destined to Fail

June 12, 2017

In pursuit of blogger clicks, the security scandal scribe has spent nearly a decade attempting to cyberbully security industry businesses. That seems to be the online site’s MO from day one. But what is the blogger really achieving?

The blogger’s most significant achievement appears to be becoming the No. 1 security industry detractor. Here is where the blogger truly rises above the crowd. With the online blogging site as his cyberbully pulpit, the scribe appears compulsively driven to attack.

When a security manufacturer, integrator, trade publication or industry association works hard and has some success, the online blogger is silent.

In fact, hard work and achievement seem to trigger the blogger’s attack response. The blogger specializes in trolling and looking for fault. He is hypercritical, quick to judge, and only sees the facts and the information that reinforce his narrow, personal world view.

Evidence is abundant on the online blogger site. Peruse the site’s “articles.” Click on one company and read through the threads. The blogger focuses on one company, one security professional, one trade publication, and one industry association at a time. Then he works feverishly, polluting the blogosphere with relentless cyberbully attacks.

In the past two years, Hikvision has become the blogger’s target of choice. As the No. 1 security industry detractor, the blogger has amped up his “coverage” of Hikvision at an impressive rate.

A quick review of the blogging site’s “articles” about Hikvision delivers some insight into the blogger’s current mission.

From March 22, 2015 to June 6, 2017 the site ran 77 Hikvision “articles” that are primarily about Hikvision. Most of the scandal scribe’s “articles” target Hikvision for insults, distortion of facts and denigration.

These statistics do not even include the hundreds of so-called “Discussions” that the blogger creates out of his comment threads.

Blogger and Trusty Sidekick ‘Undisclosed’ Perpetuate ‘Debates’

Of course it’s difficult to categorize the scandal scribe’s “articles” as many of them generally devolve into insults and denigration.

That’s the blogger’s tactic. Start with a topic that looks passably professional and then perpetuate a “debate” through comments on the “article.” Who comments on these articles? There are some regulars, but many of comments are made by the blogger himself and his trusty sidekick “Undisclosed.”

Who is ‘Undisclosed’? Only the Blogger Knows

Who is Undisclosed? Only the blogger knows. Why does “Undisclosed” show up at just the right time, asking that one question the blogger wants to bloviate about? Perhaps it’s a coincidence.

Often times, the blogger shares smiley faces and chummy banter with “Undisclosed.” It’s almost like the blogger is having a conversation with himself. Perhaps he is.

But let’s get back to the “articles” and see how the scandal scribe’s mission has evolved over the past two years.

In the roughly six months between May 22, 2015 to Dec. 31, 2015, the blogger wrote 5 posts about Hikvision. In all of 2016, the blogger upped his game, writing 34 posts about Hikvision. In the first six months of 2017, the scribe has been busy, posting 38 “articles” about Hikvision.

Blogger Lobs Post After Post

The bloggers’ readers wake up morning after morning to find that the scribe has lobbed another Hikvision post their way. If the blogger continues this cyberbullying campaign, he will post 76 articles on Hikvision by year’s end, a year-over-year increase of 124 percent.

At this rate, the scandal scribe’s readers will be assaulted by more than one of these “articles” per week for the rest of 2017. Can even the indefatigable “Undisclosed” keep up the pace?

Is the blogger’s click-bait consultant a secret weapon in his mission?

It’s no secret that the scandal scribe is currently obsessed with Hikvision. The online site has aimed its vitriol at others in the past and it will no doubt try to cyberbully others in the future.

But the industry increasingly understands the tactics of the No. 1 security industry detractor, it sees that the scribe has no scruples about launching unwarranted attacks on hardworking people and honest businesses, and we believe it only distracts from the industry’s focus on fighting criminal and terrorist activities.

IMPORTANT! This model requires non-standard firmware. Do Not Install standard firmware (e.g. v.4.1.xx) on this model. Doing so will permanently damage your system. You must use custom firmware v.4.1.25 from the iDS-9632NXI-I8/16S product page.

View the most updated version of this document here:


The I-series NVR (such as the DS-7716NI-I4) is one of Hikvision's most popular and feature-rich recorders. As such, many firmware revisions have been introduced over the years to continually ensure the product is compatible with the newest technology available. Due to the many revisions, we recommend that the user closely follows the instructions below in order to reduce the amount of time spent as well as the chance of failure.


Database Optimization and Repair

As more affordable IP cameras are introduced over time with greater video resolution and data sizes, more efficient database management also becomes necessary. The introduction of firmware v4.0 brought about a new database architecture in order to be futureproof.


After upgrading to v4.X, the recorder database will need to be converted and optimized. If you are experiencing issues where playback is expected but not found, make sure "Database Repair" is performed as indicated in the procedures and scenarios below.


Preparing the Upgrade

Before proceeding with upgrade, it is recommended that NVR configuration file is exported from the NVR over the network or on to a local USB drive.


Upgrading from v3.4.92 build 170518 or Older

  1. All recorders must reach v3.4.92 before proceeding further. Upgrading from versions before v3.4.92 directly to any version of v4.X will likely cause the recorder to fail.
  2. If the recorder is already at v3.4.92, a full factory default is highly recommended before upgrading to any version of v4.X. There is a high chance of unit failure (requiring RMA) if the unit is not defaulted before upgrade.
  3. After reaching v3.4.92 and performing a full factory default, an upgrade directly to v4.50.00 is acceptable.
  4. After the upgrade is completed and the recorder is reprogrammed, it may be beneficial to perform a Database Repair. For details, refer to the section "Database Optimization and Repair" above.
  5. To verify repair progress, you may refer to the HDD status, or search the recorder log for repair started and stopped entries. Note that while the HDD is repairing, new recordings are still being made, but some existing recordings may not be searchable until repair is complete.
  6. If you continue to observe playback issues after database repair, ensure there are no power, network, or motion detection issues. Should the problem persist, contact technical support.


Upgrading from Any v4.X Build to v4.50.00.

  1. Any v4.X build can be upgraded directly to v4.50.00.
  2. Export configuration is highly recommended before performing the upgrade.
  3. If upgrading from any v4.X version that was not v4.22.005, a Database Repair is recommended. Refer to Step 4 and onwards in the previous section.



Downgrading is not recommended. Due to new features and parameters constantly being added, downgrading may cause the NVR to factory default itself or require a manual default to operate properly.

View the most updated version of this document here:
K-Series DVR upgrade instruction
The Turbo 4 Hybrid DVR K series has multiple models and across different platform and chipset. It also has similar firmware development of other recording product line; DVR K series has also introduced the GUI4.0 to ensure the series to be compatible to the newest technology available. The new database architecture is also brought into the DVR firmware v4.0 to be future proof and for better recording search experience. 

Database Optimization and Repair

As more affordable cameras introduced over time with greater video resolution and data sizes, more efficient database management also becomes necessary. The introduction of firmware v4.0 brought about a new database architecture in order to be futureproof.
After upgrading to v4.X, the recorder database will need to be converted and optimize. If you are experiencing issues, where playback is expected but not found, please make sure to perform "Database Rebuild" as indicated in the procedures and scenarios below.

Preparing the Upgrade

Before proceeding with upgrade, it is recommend exporting DVR configuration file from the DVR over the network or on to a local USB drive.


Action after firmware upgraded 

1. Upgrade the DVR according to the chart above. 

2. Reconfirming Channel's Recording Schedule 

    - Confirm channel's recording schedule is enable. 

    - Check if the channel is on correct recording schedule.

3. Double Check Storage Setting

    - Make sure all channel are assigned to record on its HDD group when the Storage setting is under Group Mode. 

4. Perform Database Rebuild locally. 

    • Some version above support Database Rebuild via web access - K51 and K72

    • Perform Database Rebuild regardless if system is having any database issue symptom. 

    • Database Rebuild process is average ~30 to 60min per TB. The process may still varies depends recording data.

    • After Database Rebuild - Check log to confirm Database Rebuild has went thru properly. 

    • If Database Rebuild Started and Stopped log has been log only within few minutes. Database rebuild may not has been completed properly. It is strongly recommend performing the Database Rebuild again.

    • To check log > System > Log > Information > Database Rebuild Started and Stopped.

    • If the log option is not available - access system via SSH can also obtain similar result.

5. Recording Data is still missing after database rebuild process. 

If the data has not been recorded or has been overwritten, Database rebuild process is not able retrieve those lost data. Have the system upgraded to the latest available firmware version above to prevent any future data lost is strongly recommended for all application.





In light of the global semiconductor shortage, Hikvision has made some hardware changes to the DS-76xxNI-Q1(2)/P NVRs, also known as “Q series.”


These changes do not have any effect on the performance, specifications, or the user interface of the NVRs. For the ease of reference, these modified units are known as “C-Version” units. This is clearly indicated on the NVR label and on the box by the serial number.


The only difference between the “C-Version” and “non-C-Version” is the firmware. The firmware is not interchangeable:


  • The C-Version NVRs must use firmware version v4.31.102 or higher.
  • The non-C-Version (Q series) NVRs must use firmware version v4.30.085 or older.


Please do not be alarmed if a “Firmware Mismatch” message pops up on the screen during the firmware upgrade. This simply means that the firmware does not match the NVR’s hardware. Simply download the correct firmware and the upgrade will go through without any issue.

By downloading and using software and other materials available via this website, you agree to be legally bound by HIKVISION General Terms of Use . If you don’t agree to these terms, you may not download or use any of those materials.

If you are agreeing on behalf of your company, you represent and warrant that you have legal authority to bind your company to the General Terms of Use above. Also you represent and warrant that you are of the legal age of majority in the jurisdiction in which you reside (at least 18 years of age in many countries).