Acigan

TO kronrnbergerJ Yes the system usage is a bit higher. Such is the nature of new and added features. Here are some things you can do to reduce the overhead somewhat. Some or all may apply to your box. Without being there at the keyboard myself, I can not actually see the issues but you can go thru some of the items below and examine things for yourself and see if they help. *** Control Panel / System / Performance tab.... In the panel for Swap Files, turn off Windows management of the swap and only set on swap to your FASTEST disk drive. Drives can be slow or fast depending on platter rotations (7200 rpm is fast, all others are slow disks). If more then one Drive (a large disk is partitioned)..... set the swap to the same drive letter where the OS resides, this is usually the C:\ drive. Turn all the others off. Now for the Minimum setting, use 1024 mb. For the Maximum Setting use the formula of 1024 x #_of_Gb_of_RAM_Memory. For example a 4Gb Ram machine would be 1024 min and 4069 max. an 8Gb box would be 1024 min and 8192 max. This now makes a fixed swap file that can expand as needed and avoid the OS overhead of constant monitoring the swap file. It will only expand if Resources exceed the current allocated size. Once that allocation is reached, the swap file just remains that evaluated size until it is exceeded again....and keeps doing that until the max size is reached. If a Swapfile is at max and the OS still wants more..... you have to begin killing apps or unloading autoloading ones that are not being actively used. In most cases the kill/unload never has to be done if the formula is used to set the sizes. Most new drives also have hardware caches built in with the cache size max being 8Mb..... some are as low as 1Mb ...but they are always in multiples of 1024 bytes. The formula usage will create even block sizes in the Gets and Puts of data from the swapfile to RAM and that will also reduce uneven blocking or multiple data block calls just to fetch swap data. This reduces System Resources. After the change, reboot to make effective. The tweak will take a few days of active use to fully be realized as data is shifted around on the drives. SmartDefrag runs will assist in data movement also during those few days. *** Go into ASC and its Toolbox applications and examine each ones Settings. Turn off all of them from auto-starting at boot time except ACS itself. That you do want loaded automatically. But all the others can be manually called from the toolbox as needed. This will reduce the background tasks running and just waiting for you to be idle in order for them to fire up and do things. If you dont want manual control of some functions, set them up on the Win Scheduler to run. Some have these options in their Settings already, but if not, create them in the Scheduler application itself to run when you know you will be away from the machine. I run my SmartDisk this way (Idle after 30 mins away) and my DriverBooster runs only once a month this way. They dont load at startup but still run under a form of automation, managed by Scheduler and the OS. *** Review your running Services again in the ASC Speedup tab. Turn off Turbo Boost, go thru the settings again and shutdown jobs and services you know you do not use or need. In Win10, MS has this little habit of modifying Service setup records with each major Windows Update patch. So if you know WinUpdate has installed a large Cumulative Patch to the box, re-review your turbo boost to see if the then known entry for a Service was removed and replace by MS with an updated one that has the same name/description. These are values they change and to the common user it appears to be the same, but under the hood, the old records were removed and replace with new ones. This can throw off Turbo Boost pointers since they no longer point to the correct Service to manage. *** Ensure SmartDefrag is performing its pre-boot functions. There are some files that just can not be managed for performance if Windows OS is up and running. The OS has them open and using them. Therefore, SmartDefrag needs to know its allowed to manage them during boot time. I use the setting that says Once per day at first boot. It only takes about 30 seconds extra to boot and those system only files will be much better shape for performance then before. The Swap File referenced above is one of those files. Directories are another and the MFT, Master File allocation Table is yet another. You see them in SmartDefrag as different colored files. The general rule is that if the OS has it opened, it can not be managed or tuned, hence the pre-boot settings that manage them in SmartDefrag before the POST process completely turns over machine control to whatever OS is loaded on the harddisk. There are some more tweaks here and there one can do to regain Resources but try some of these things above and reboot. Monitor normal usage of the box for about a week then re-examine it again. Other things can be done after that. But as a rule, We all want more features and options with every release of software, but we forget as users that the cost of wanting .....results in More Resources. The best example of this is Windows itself....what used to fit on a 20 gigabyte drive and 512Mb RAM with room to spare for apps (Win 3.1)..... Now needs 64Gb min space and 4 to 8Gb memory just to fire up and present the desktop...thats not counting optional OS features or even your own applications. This is the price Users must pay for what they want. I had a developer that worked for me once say it the best way to a client that did not like buying hardware just to upgrade their PCs....... she said in a board meeting once to the client, " ....Eff that......if you want a car to perform and respond, you install a V8 engine. Its not going to fit in your volkswagon of a box you have parked in the garage. You can pay us now and ATTEMPT us to cut the volkswagon up and shove in the V8 and then pay us again later when the car falls apart from the power, or you can pay for that Lambo thats already made for speed and has the V8 in it.....its up to you.... " -- The client took her words to heart and ponied up all the funds for their staff and new PCs and we cut setup and install and everything else by a third of what they would have otherwise paid. They learned that rule as users that with every new thing wanted, there is price to pay......Resources or dollars. They elected the resource increase route that day. Let me know if any of the above tricks helps on your box.

TO JimmyPop. There is a way to make Windows Defender AND IMF work concurrently. This is under the assumption the IMF version is the free version and not the PRO one where the virus protection is active. In the free version, only the malware feature is active, and one needs to have a virus program also. Windows Defender can be used in this case for Virus protection so a PC is protected by both Defender and IMF. A hack to make Defender work with IMF in this case is not a complicated one, but it does require a bit of understanding of the machine's Security and the Registry. It also requires one to perform a few manual steps after each reboot, but once the process is understood and learned, it becomes quite simple. Since this is not a MS Hack forum, I will only describe in general the steps and not the actual hack steps so I dont violate any forum rules here. Those with full understanding can pick up the generals and know what Im referring to. Also, ioBit can read the generals and maybe come up with a logic change to IMF to prevent the registry disconnects in a future release. First, you must be an Administrator class user to even attempt. If not, dont bother, you wont get past the first action. *** *** Log in with an Admin ID. *** Open Defender. It will be red and disabled. or yellow (lately) and in passive scan mode. *** Load MSC Services console. Stop the Windows Defender services if they are running. *** Load RegEdit. Locate the Defender Keys at local software, Windows Defender. *** Change the OWNERSHIP of the WINDOWS DEFENDER keys in the Registry from SYSTEM to ADMINISTRATORS using REGEDIT and right click the left master key for Permissions. and Security. This allows Admins to also modify the Defender Keys. Only the OS in Win10 is now allowed access to these keys so thats why were changing back to also allow Admins. So an Admin using Regedit can manually modify the values. *** Close and reload RegEdit to make the Permissions permanent. Relocate the Defender Keys. *** Change the DisableAntiSpyware key to zero. *** Change the DisableAntiVirus key to zero *** Change the ManageDefenderProductType key to 2 *** Change the PassiveMode key to a zero. *** Change the ProductStatus key to a zero *** Change the ProductType key to 2. *** Use MSC Services console again to restart the Defender services, (there are two of them, one for defender local and one for defender to scan networks. *** Wait about a minute and watch the Defender windows, it will change from red or yellow to green and go active. Defender will now be active using both its virus and malware validations features. IMF (free) will also be active monitoring the malware and websites. The PRO version does everything so these steps are not needed for Defender. The issue is a well known one to Microsoft. They are not very proactive in its correction and will have users run diag and removal tools for 3rd Party Virus Programs, even posting links to other sites away from the MS Defender forum to go and fetch the tools. MS does not want to state in a public forum that Defender has security holes they have not yet located and corrected. This minor flaw occurred in logic when MS elected to incorporate Defender into the OS in Win10 from a standalone application. There are many posts on MS Forums as to the problem but MS will not admit to the fault less they loose the customer base that Defender has gathered. The bug is in Defender and how it assumes that ANY 3rd Party application that deals with any form of virus or malware, is a stand-alone-full-featured application and that Defender is to shut down at the OS level and the 3rd party app takes over. To make an global patch, MS just securited the Defender Keys to only SYSTEM owned and Applications can only read the values. There was also some Windows Updates to these areas in the Win10 Cumulative patch about 2 or 3 updates ago. Just prior to Win10 Anniversary Edition Update release. Win10 AE has all the patches inclusive in it that locked up Defender, instead of the sequential patches that did it slowly over time on client boxes. The steps I listed modify the Registry values that Defender examines at startup (boot) that say if a 3rd Party app is present. In the case of IMF, one is, the malware feature of IMF so Defender just shuts down. Defender in Win10 is always present and loads at boot time, its part of the OS now. If a 3rd Party app is present, it now disables itself after about a minute, with that time being active until boot and startup finish their steps and the 3rd party app fires up and begins actually monitoring the system. All that these steps do is restart Defender and tell there is no other app doing the monitoring, leaving IMF to run in the background monitoring, but Defender doesnt know anymore that it is there also. If you do not understand the Registry then DO NOT attempt the steps. If you corrupt a key you can render a PC unusable. To IOBIT: Perhaps the free IMF or an ASC scan on the Registry values can be examined and modified to allow the free IMF to run concurrently with Defender without the messages popping up all the time that both application are no longer monitoring. IMF free always is in the background, so that Security Center message is not actually correct, but Defender now shuts down if IMF free is on the box. If IMF is able to inherit runtime permissions of the keys from SYSTEM, leaving the OS to retain ownership as MS intended, then IMF could modify the keys to allow it run concurrently with Defender when its only the free version. The PRO version needs Defender to shut down properly or a user would be double scanning everything for viruses. Hope this Helps.

Cicely? Have them double check the logic in FaceID. Around the area where FaceID is to shut down. I dont think its shutting down properly. It stays running once the default Owner Image is captured. When you open the ASC Beta 2 PROTECT tab, and click on FaceID.....if its not active it will load up (verified with Windows Task Manager). It stays active even during reboots. (as it should) But if you click on the button in PROTECT panel to turn off FaceID, ....it stills remains running (again, verified with win taskmgr) The button indicates its turned off, but the task is still active in memory. It should shut down and no longer be running in the background using up system resources. I have a gut feeling that since the initial capture image is present, and there are no time settings to tell it not to be active, the logic is probably falling thru the process and not shutting down the procedure properly, looping around and remaining active. To see an example just load up the windows task manager and look at the active ASC tasks. Tell FaceID to turn off with the button and you'll see that it says it off on the panel but is still active in the background in Task Manager sucking on resources. I noticed it when I was in CAD program and had some poor response when rendering objects. So I was looking at whats sucking up the resources. I shut down FaceID on the panel but it kept on being active in the background. I ended up having to terminate it manually. At the next reboot, it fired up again in the background even though the setting in the PROTECT tab panel shows it as off.

TO Jby1956: another trick to try if the keyboard driver is locked up and wont allow typing, but you have mouse actions, would be to right-click START BAR, select the TOUCH KEYBOARD BUTTON and turn it on. This will give you an icon on the start bar for virtual keyboard that you can click with the mouse to circumvent the locked up physical keyboard. Then go make sure you have the Win10 patches and the other stuff I said above.

TO Jby1956: I run the BETA on a Win10 box. It does not act in the manor you describe. Your issue sounds more Windows related then ioBit related. Check all your current Windows 10 Patches. Verify you are on WIndows 10 Anniversary Edition by this time. If not, get it for free from the Microsoft Store. There is also a service patch as of this week to the Anniversary Edition. Your issue may also be outdated Drivers. if you dont have it already, fetch the latest version of ioBit's Driver Booster 3. In the settings option, unclick the option that looks only a drivers offered thru the Windows Update and look for drivers that are newer, like from the manufacture themselves. The setting Im referring to is on the GENERAL tab, scroll down and says "ONLY DISPLAY DRIVERS THAT PASS WHQL TESTS" --- Uncheck that option, rerun a driver scan and update drivers that it finds. Reboot cold not warm, meaning, a complete power down, wait at least a minute or more for capacitors to discharge their loads to ground, then power the box back up. It sounds to me like you have both a drivers problem and Win10 Patch problem. Once youre back up, double check your Windows Settings to make sure that Win10 is fetching and applying patches automatically. Microsoft releases their OS patches once a week, on Tuesdays for all the supported OS versions thru the Windows Update function. But if the user does not use the automatic apply feature, the patches dont ever come to the box and have to be fetched and applied manually.

i would suggest that you go into ASC 9 SETTINGS and unclick the option to load at startup. Both will fire up when Windows starts up and will run concurrently. I haven't noticed any conflicts per say, but both ASCs will be active sharing some settings and at other times having separate copy of settings. Mostly in the area of what to clean up. With both ASCs running you are taxing system resources. Normally this would not occur since the Production versions uninstall the prior installs, but because this is BETA, it is loading off to the side of the Production. I have Beta loaded onto two different machines. One has the v9 still installed and the other v9 was uninstalled manually prior to beta install. The one with v9 still installed was running both versions at Windows Startup so I turn off the setting to load automatically. It does not appear to effect the Beta logic on either of the two boxes whether Production is there or not other then the dual concurrent running of the ASC Production and Beta. The beta is even loading into its own folder under Program Files. Just turn off the setting so the Production doesn't start up. That way when Beta testing is complete it can be uninstalled, the setting turned back on; and your box is back the way it was in preparation for the actual v10 Production release. Hope this Helps

You're welcome. Let them all know to keep up the good work on those products.

FYI, translating ASC 10 to my language, I have changed the name of the Performance Monitor of the mini window for the resources as "Resource Manager", as the button on the Performance Monitor is defined as Resource Manager which opens the concerned mini window for resources. that was exactly my point. The previous panel even says "Manager" in the button. The resulting panel that was then opened allows "management" actions but the overall title bar indicates monitoring functions are still the focus to the user. *** When the human mind views display screens, we are taught from childhood that the top of the thing we are reading is the Subject Matter Overall. Then Indexes (aka tab buttons) to jump quickly to the subject that is desired the most,..... then we start the actual detailed process of eye movement and reading. If a Heading or title bar is not labeled correctly from the start of that habitual process, it can cause disconnects in the way the person interpolates what they are physically seeing with eyeballs and what they are seeing in their minds-eye. We see the title bars everyday but we dont always pay physically attention to them. But the Minds-eye does. It is the bases of even tricks used in advertising and getting you to buy things without you even knowing why. Think of the right-hand spammed banners on web pages. You physically ignore them but the eye did see them and the Minds-Eye did process them. Now when you sleep later that night, the mind begins it sorting process and filing all it captured that day (memories and dreams) and for some reason when you wake up the next day you have an desire to go buy a partictular product. Thats an extreme example of the topic presented but it is commonly used on web pages and it does produce sales results. So design care mus always be given to panels to ensure they do not misdirect, misread or misinform a user. Leave that kinda stuff to the Ad Spammers. Is why we hate them to begin with. When we are at computer screens we are relaxed in that type of misdirection that can happen which is why it is used by the Spammers so much. Were not on guard. So to make a Software Product feel solid and reliable to a user, one must ensure there is proper direction and action when presented to them like on a Panel. Sometimes even the simplest typos made when a panel is first created can result in actions never intended by the creators. *** I personally dont even like the idea of a bridge panel between a monitoring function into Management functions. As an Admin, if Ive locked up a user from accessing task manager because the user cancels running background tasks needed for a network, so their Lunchtime game runs faster, there was a reason for not allowing that user access to cancle tasks. Now I would have to take away Perfromance Monitor from him also, since that user could circumvent the lock and use that popout panel to also cancel jobs. This is why the two functions should never be bridged. Monitoring is READ ONLY. Management is WRITE ENABLED. That bridge the popout now allows gives users Admin Access to Tasks when before there was none.

awe, thx, but homework isnt my intent for CIcely. Infact quite the opposite and trying to explain technical things in a format general users will grasp. I fully understand the task of producing a Software Product being that its my profession also. Just trying to take off some of the explanation load from ya all so your focus can be on the Release, not explanations to users as to how things work or why. Keep up the good work. Ive used and loved ASC since its inception. It gets better and more feature loaded with every release. My favorite feature in the BETA so far is the FaceID enhancement. Im glad you all have brought a new security feature to older boxes that are not equipped with Bio Devices and only a camera. I think many users will use that feature for an added layer of protection.

BETA v2 installed. Item 1. This time Im posting regarding the Facial Rec module. First off, Nice. It Echos back to a few years ago when Lenovo used the feature for Log Ins on their PCs. Before the days of Bio devices. For those users that do not have Bio Devices on their boxes, and only cameras, the feature gives them a layer of security that is not otherwise available to them. Good Job. Now Im taking off the User hat and putting on the Designer/Developer hat. In the setup options for the Facial Rec, FaceID panel, under the SETTINGS tab, there is the first setting option called EXCLUDE PERIOD. As a Developer, I understand NOT-Logic very well, but the normal Layman and User will find the description and explanations somewhat confusing. The reason for this is that human mind prefers positive interactions over negative interactions in the way it processes and thinks. When Developers create options and logic, they are totally comfortable with both Logic and NOT-Logic. ie, Exclusions. Everyday Users are not. So with that in mind for a more understandable setting as to when the application actually does it processing, here is what I would suggest as to how to go about describing and presenting that setting. Change the viewpoint from being EXCLUDED PERIOD (negative and NOT-Logic(al) to be INCLUSIVE (positive and processes in the mind in the normal flow of human thinking) Instead of reading as "FadeID will not identify intruders when they use your computer during the excluded periods you add" This being a double-negative in phrasing with the words NOT and EXCLUDE in the same phrase, in other words a Positive phrase using double-negative wording. Change the phrasing and wording to be in the actual positive manor the underlying logic is actually doing: "Enter the start and end times you wish FaceID to monitor your computer." Now the double-negative phasing is gone and the description is more straight forward and understandable to the common user as to enter times they want FaceID to look for someone accessing their PC. The mind now processes the phrasing faster and with more comprehension then when using the double-negative wording that makes one sit and really think in a manor they are not used to using, being that not everyone processes NOT-Logic quickly and understandably as some Developers do. The setting is basically informing the FaceID app as to when to watch over the PC. Not when a User is sitting and using it. Item 2 The BETA 2 downloaded and installed with two of the setting values already predefined in that Exclude Period setting. When you understand the concept of NOT-Logic, the shipped setting will actually allow users to access and use a PC during those time frames. The settings indicate to exclude monitoring violations during the time frame when PCs (think businesses and work) are not actually in use. From a Security standpoint, THIS IS THE TIME we want to monitor for violations. The normal user of that PC is has gone home and the PC is in a office or cubical unattended. This is when the FaceID would be running to capture who is attempting access. Since the double-Negative is in use there, Excluding these time periods would be logically flowing thru code to be the times to NOT to process, when it should be stating the times as to actually process and capture violations. Understand? Shipping the two settings places a users PC in a mode NEVER to capture. The user is using the PC during normal work hours and NOT using it during the shipped settings time. But since these are EXCLUSION TIMES.....the end result is that FaceID will never capture any violations when installed. The Release version should not contain any settings at all. Let the user define it as part of the steps of activating the FaceID module for the first time. This can be done at triggering the settings to be presented when the slider button is first activated to the ON position in the previous panel. Then the user defines to the app, the times of day they want monitoring to occur in the settings. Change from the Double-Negative thinking to a single Positive manor for the settings. It will save a lot of Help Desk calls in the future on that module and even some future bugs being introduced in later versions because the NOT-Logic developer left ioBit for greener pastures and now a new developer is has to modify the logic and the new guy hasnt a clue on the understanding of NOT-Logic principles. He would eff it up royally in logic..... and the End User would get buggy code or a feature that never works exactly right. They would stop using it after time.

TO CICELY. Id like to point out a nomenclature item in the pop out panel of Performance Monitor. The popout Im referring to is when you press the <- button in the panel title and the expanded popout replaces the main panel. The popout then shows RAM, CPU and DISK usages in larger circle graph formats and "Processes with high RAM/CPU/DISK usage" listed under the circle graphs. Heres the nomenclature issue. Performance Monitor no longer makes sense (Im in Designer/Developer mode here, not User mode), since the definition of a monitoring application should not be allowed to "manage" whats being presented. Management of the tasks is being allowed via the X buttons and the END TASK larger button below if one checkmark-highlights a task. So the proper nomenclature for that popout panel should be Performance Manager and not Performance Monitor. If its to be a strict monitoring application (as I think it should remain being) the functions to cancel tasks should not be presented. If its to become a high level task manager application, then the nomenclature of Performance Monitor no longer should apply. I know this may sound silly to most, but when I have my Designer/Developer hat on and reviewing things, stuff like this catches my eye and stands out. A monitoring app doesnt manage and a management app doesnt monitor. Its two distinct functions in the Computer Sciences realm. One watches, the other performs actions. Its the difference of READ verses WRITE of data. Read only looks at data, the Write acts upon it. A possible solution would be to have that popout panel's title be modified when the arrow is pressed to say Performance Manager instead of retaining the Performance Monitor nomenclature. The User would be using that panel anyways to manage excessive tasks that are listed. I also think the return arrow is misplaced. Its on the right in the title bar. It should be on the left where the ASC icon logo is. That position has become a defacto standard in title bars both on PC platforms and on tablets. Since ioBit also has tablet apps (yes I use them also) the Return arrow then becomes standard placement on all platforms. This shows Unity of Applications across all the platforms ioBIt supports and develops for. Use an Android version of Performance Monitor on a tablet would look and feel the same as the PC version. Only the logic it was written in would be different, but that, a user never sees. On the same panel, the phrasing of "processes" seems non-intutive also. "Tasks" would be a better column heading phrasing since its used more to represent high level EXE logic executing then processes. Tasks are to Applications as are Processes are to Threads. Something for the Futures List on that panel would be a Settings button, where one could define the baseline values of running tasks that would then trip the user defined baseline to appear on the list. Reason I say that is i see tasks being listed as using High DIsk Usage but are not actually in excess of what their function actually is. Your own apps even show up there, SmartDefrag for example shows as High Disk Usage, but its very nature is just that. Moving data around. Maybe even a Baselines setting and an Ignore List Setting like other apps of ioBit have. So a user could enter tasks that are ignored and not ever displayed, SmartDefrag for example could be entered and ignored under disk usage since we know it will result in very high disk I/O by nature of its function. SmartRam and Malware Fighter are also doing the same thing in the RAM usage display. Again, their very nature would be high Ram usage. One is cleaning ram and the other is scanning ram bit by bit as bytes move thru the chips. They could be set to ignore by a user. For the Baseline setting, have a user define the amount a task must exceed first, in order to be listed. Reason being, Im currently looking at an idle box at the moment (not this one Im using) and the panel is reporting that the Windows Logon Application that uses 2.92MB of RAM is High Usage. Its not. Thats is normal usage values and that task only becomes active and wanting more then that when a User Logs into Windows, once logged in its mostly waiting for log out and the 2MB or so it uses is just logic in wait states and doing repeated checking for logins or log outs. Setting a BaseLine setting option one could set it something like 25MB or higher and all the small apps in resident mode and just waiting would not show up. If for some reason they flake out and begin to run amok, they would exceed the normal ram and trip the baseline value setting....thus be listed then as in actual HIGH Usage. Im not picking on MONITOR.exe per say...... Its just an app that is before me day in and day out so I see it all the time on my desktop. I have other comments regarding the other modules that make up ASC but they are mostly minor things like why the hell does ioBIt change panels around with every Release....but thats must me. Sometimes I like the changes and other times not, throughout all the prior versions and other times I think, hmmm, someone there really likes panel designing and what-ifs. I do like the new format of the button shapes in the Beta. Different. the angled buttons make a statement that these applications are different then your normal run of the mill oval buttons. Nice. The rearrangement of the SCAN items order did make me look at that panel somewhat. For so man versions the order didnt change and one got used to watching the Scans process thru each step in a set order. The underlying function is the same but the order of scanning did stand out to me. Maybe Im too old school in my Design thinking and follow the rule of logic that says....if it works, dont modify it unless its broken. Even something as reordering a process at times can have unknown effects in logic paths and cause hard to locate bugs. Then again, I know of Developers that ensure their Careers in just such a way.... Let me know your alls thoughts on the panel stated above. Id like to hear the feedback from you all about it.

I can explain some of the differences in reported values. You can see them in action if you fire up TaskMgr.exe, MS Performance Monitor MMC plugin, and the ioBit Performance Monitor, MONITOR.exe. If you place all three side by side and just watch the CPU usage values for example, there will be differences at times. Heres the reasons for them: Both Task Manager, and MS Performance Monitor MMC plugin are native Microsoft applications. In being that, one would expect they would show the same values as they execute but that is not the case. Within the box may be a single core, dual cores or quad cores of the actual processor. When more then one core is involved, the gathered information will be fetched a CPU core at a time and then averaged. To us humans, the processes appear to be running all at the same time but in the reality of the nano and pico-seconds, tasks are being threaded one by one into the cores. So in our three monitor tasks running example, there is a first, a second and a third task waiting in line. Sometimes, depending on the number of cores like a quad core CPU, all three end up in 3 of the 4 cores at the same time, each looking at the other cores and evaluating what they are processing at the moment, and NOT always including themselves in the evaluations. So MMC.exe in core 0 sees core 1, 2 and 3 and evaluates values, MONITOR.exe in core 1 sees core 0, 2 and 3 and evaluates its results and TaskMgr.exe running in core 2 sees core 0, 1 and 3 and evaluates its results. Since the three apps in question are written differently and even different code-token sizes being executed withing the cores, they all three evaluate different results even within the same CPU clock tick cycle. Even differences of if the EXE module is compiled using x32 or x64 token sizes makes a difference. An x32 app running on a x64 core will bring in 2x the tokens per tick then the larger x64 based code token produced by the compilers when the EXE is created. Now keep in mind that ioBit apps run on both x32 and x64 based processors and the logic is more then likely x32 bit for both. (am I correct in that assumption, ioBit?) because we dont click seperate links for x32 and x64 when we bring the logic to our boxes. So now there is a new factor in the differences mix..... x32 code running on x64 cores. On an x64 OS, Microsoft has optimized their native applications for the x64 bit cores and MMC.exe and TaskMgr.exe can be different then their x32 counterpart EXE files. So on x64 boxes, run the MONITOR.exe (x32) and it produces some slight differences in results because it is either processing x2 faster as two blocks of code are moved to and from cpu for execution, or its running x2 slower then the x64 MMC.exe and TaskMgr.exe, because of extra paging needing to be performed to bring in code into the CPUs. There is also the factor of the Software Development Kit (SDK) overhead of MONITOR.exe verses native MMC.exe and TaskMgr.exe that is written native for the operating system and may not even go thru the logic bloat layers of the SDK. So again, MMC and TaskMgr would evaluate faster results then MONITOR. Now we get to the MMC plug in verses native code of TaskMgr verses SDK layer of MONITOR. The MMC.exe version of Performance Monitor is a plug in to MMC.exe and not a fully compiled App. This means that it also has an extra layer of cycles and processing deep in the cores to fetch the logic compiled in the DLL files of the Plugin. MMC.exe is the basic general logic all the plugins use. Each plugin has its own unique logic in the plugin logic that is not common to any other plugin. So MMC.exe has some extra logic cycles to fetch and execute the code-blocks from the DLLs that other performance monitor apps would not have. This shows up in the other apps as MMC.exe using more CPU cycles then the others, just to show the same results. All these factors and even more not explained here are why monitoring is always averaged. If you want more exact monitoring, use MMC and set up monitors on each of the CPU cores individually and dont use the ioBit MONITOR.exe at all. Its a high level monitor geared to general users and not exacting techie types that examine every cpu cycle tick. It even averages the CPUs on multi-core machines to present a single value in the panel. Its used to show a generalized usage and reporting values. If something doesnt look kosher then, fire up MMC or TaskMgr and examine in more detail. As Cicely said above in general terms, some differences are normal. I hope Ive explained some of the reasons for the normalities in further detail. There are many many more subtle things that are also occurring within the CPUs and I only touched on but a few that can produce slight variations in results. With all that being said, the ioBit modules are not reporting incorrect results, they are just reporting the results from a timeslice that is nano or pico seconds ahead or behind other monitor applications also running at the same time. Same time to us humans, Hours, Minutes, Seconds, are lifetimes to the CPUs in their time scales. They are not processing things at the same time, they are processing them in a defined timely order, defined by oscillating clocks in the mega and gigahertz range ..... in other words.... single file into one or more cores on the processor chip, all timed and orderly...., just very very fast to us. Think of it as Cars at a traffic intersection. the light turns green and x number of cars go thru, some faster or slower then the green light before or even the one to follow. But if you sit and count them over say a time cycle of a hour, then sum up the number of cars per hour, and divide by 24 hours, ..... you will have that average number of cars (logic block tokens) flowing thru the intersections (the cores). Do that for a month and produce the results for review. Thats what monitor applications are actually doing.....very very very fast. So there will be differences between apps that do that since they dont always even include their own logic blocks executing in every pass. Doing so skews the results. But the others saw the blocks and skewed their own values by not including their own blocks of code. They cant, they evaluate a logic block of their own if that block is the the one that does the evaluations. Its not in core yet to execute the results. See how freaky it is inside the cores? Now you know why Developers are freaky kinds of people. I hope Ive explained things and given you things to ponder on or to further understand the box thats before you in how it performs the tasks you ask of it.

I have also loaded the Beta onto an older machine. One running XP. (dont laugh, youd be surprised how many users still have them in their homes and need support) Because of this I keep one around and fired it up and uninstalled its production version of ASC and loaded up v10 Beta onto it. So far so good. Everything is functioning as expected. No crashes. The Beta even found some deeper things to fix on the XP box then the version is was running (a 9.x version). Mostly in the area of Performance.

Sure. No problem. First the basics. My Testing Box is a Lenovo G50 laptop with an external display attached for dual monitors, laptop display and the external...the displays are logically linked via windows extended desktop. laptop display is monitor 1, the primary, and the external monitor is Monitor 2, the extended display. The physical layout is Monitor 2 above Monitor 1. Items are dragged up off the laptop display and placed on the external monitor for easy viewing (glancing up from laptop). Laptop display is then used normally for test purposes as any user would. M2 allows monitoring and debug panels to be open and viewable with just a glance upwards. Windows version running is Windows 10 Anniversary Edition. All known and advanced MS patches applied. (Im a MSDN member and receive advanced patches to test also). Disk drive is a Western Digital 1 terabyte drive and it supports SMART information fetching and reporting. Any search at Lenovo.com on "G50" will give the full hardware specs. The box is factory with the addition of an external usb drive I have apps loaded on I use everyday. (aka a usb harddrive used instead of a flash drive) *** There are two issues with MONITOR.exe, the Performance Monitor app. First is the fetching and displaying of the S.M.A.R.T. data from known SMART devices such as the temps, fan speeds. When the Performance Monitor is expanded, there is a double down-facing arrow to further expand into the SMART data information. There was a prior bug in earlier versions of MONITOR.exe that when the SMART info was expanded, it would fail and a link was there to report the fail, and a response message saying ioBit would examine and correct. That issue was resolved at some point in the ASC 9x and SMART info was being fetched and reported. In the v10 Beta, that issue of failed info being fetched is back. I saw a post above regarding the SDK for win 10 and that may be the issue with that piece of logic. *** The second issue with MONITOR.exe is the proper placement of the panel on the Windows Extended Desktop. Again, referring to the test box physical setup, Monitor 2 the external display is physically located above the laptop display. Extended Desktop allows objects to be dragged and dropped upwards onto the display. (ie, 2 over 1) and the Windows Desktop is logically seen as a Portrait format and the two monitors cut the portrait format into two logical Landscapes layouts. The Extended Desktop feature of Windows doest have issues with the layout. Things can be dragged up onto M2 with no problems. However, MONITOR.exe will not allow the panel to be grabbed and moved upwards past pixel row 0 and will be caged onto the laptop only display (M1). As a developer myself, I would examine the logic with the evaluation of the mouse location during the grab to relocate the panel. The logical pixel would be going negative due to being moved up above row 0 and into the M2 pixel mapping. Just off the top of my head, it appears to me that MONITOR.exe responds to Physical Pixels and X/Y coords for panel placement and not not the Logical Pixels (which may be negative or larger values then physical displays) of the Extended Windows Desktop. Since that initial post, I have found that if MONITOR.exe is grabbed on Monitor 1 and first moved to physical pixel location 0,0, the panel is then able to slip thru the pixel lock and be relocated up to the external display (M2)..... it can not be properly placed onto any position on M2, but it does slide up with the X of the X/Y logical pixel always being locked to zero. This results in the panel only to be placed along the left hand side of Monitor and not moved anywhere else within the Extended Desktop of M2. That leads me to conclude the pixels are using physical coords of the X/Y since one X/Y-coord is locked to zero and the other X/Y-coord is evaluating the proper logical value from the mouse location within the extended desktop. I realize some of that explaination may sound tech-deep, but to the guys/gals that are in the code and looking at the variables and know that stuff..... they will understand the text. Most developers that use Windows Extended Desktop will place displays physically Side by Side and the X/Y coords rarely go into the negative, and even if placed over.under, Monitor 1 will be above Monitor 2. This also masks the values of the logical negative pixel rows. But by placing M2 over M1, the extended desktop logically maps into the negative values for Rows, since objects can be dragged up off of M1, past X/Y coord of 0,0 and into the negatives since M2 logically maps the desktop above pixel row zero. The end results are logical pixel values of -1024/-640 for example when objects are dragged onto M2 above row zero of M1. A simple way of examining the actual X/Y coords of the configuration is to use a dev tool to display current desktop pixel location of the mouse. Moving the mouse up and into M2 will result in values not normally expected by developers or logic, but is fully supported by Windows and the Extended Desktop feature. So coding for the Logical values returning from the SDK calls and not the Physical screen coords should always be used since users can place multiple monitors anywhere where physically able to, and in extended desktop configuration, define which ones are M1, M2, M3...ect. Row/Column 0,0 as the upper left hand absolute coordinate and no negative values allowed.....is no longer acceptable anymore from a code point of view. Hope this all helps. *** I saw the response-post also about also using the thread for future suggestions. I will hold my comments back about it even though in my view its way past that point in LifeCycle. But I understand.

4. The Fix command at the results of a scan should be such that it only fixes a particular setting of Scan results in view. As it is now, the Fix button "fixes" all results globally. I would like to see this Fix button operative for each scan result category separately. This does not need to be reviewed or changed. What the user wants is already active in logic and has been there in almost every version. The user is not executing the scan correctly. The user has the SCAN ALL check box turned on. This is telling ASC to scan all the available things to fix and the resulting FIX button would then fix all that it found. This works. What the user wants is a selectable scan and fix.. This also is already supported in the application. This user needs to UNCHECK the SCAN ALL box, and select only the ones they want to scan and fix. The results of the scan will then present the FIX button that is then clicked to fix what was found, nothing else. There is no SCAN ALL, Fix Selected.... that's backwards and borders on mind reading. Computer Logic cant yet read our minds to know what to eliminate as we are looking at a all inclusive results and thinking in our minds 'I want to skip that fix'. You scan selected and fix what was selectively found. Or Scan ALL and fix all it found to fix. Run the type of Scan you want to fix selectively. Do it right. And dont come post that youd have to run multiple scans/fixes because the times and corrections are the same whether you do them one at a time or all at once. or run ALL and then drill down the expanded lists and click the IGNORE on ones you dont want to fix. Either way you do it .....it still results in another scan or two to fully fix. So just Scan ALL and Fix all and save yourself some time and get it done and over with...... log off then and go spend time with family instead of wasting it at a PC tweaking individual settings one at time.