A windows 8-like Task Manager for Windows 7 ,work in progress!


Recommended Posts

Raa

You should also make a Windows 7 task manager for Windows 8.

No.

Link to post
Share on other sites
  • 2 weeks later...
  • 2 weeks later...
Carbon Fiber

Update! August 06 2014

Do you have a changelog?
Link to post
Share on other sites
  • 2 weeks later...
Xahid

Good work Hanrui.

Thanks for this Task manager :)

Link to post
Share on other sites
  • 3 weeks later...
MidoMan94

Thanks alot , i have been following your work and i just registered to say thanks , i am glad u fixed this tool , even when it was buggy i kept using it

 

Thanks , Hanrui

Link to post
Share on other sites
  • 3 weeks later...
Gabee8

Hello!

I start DBC Taskmanager Windows 7 64Bit and exit this error dialog: whoops!

post-334490-0-51181600-1412455253.png

  • Like 1
Link to post
Share on other sites
  • 1 month later...
Hebert Leandro

Nice work man. In my pc program close on "Performance" tab and show "Whoops" kkkkkkkk.Others it work. 

 

Windows 7 (x64) SP1

Intel i7 950 Bloomfield 1366

Gigabyte ga-x58a-ud3r

G.skil 2x 4GB Dual Channel XMP@1600

Geforce GTX 680 @ SLI

XFX Pro 650W 

Link to post
Share on other sites
  • 4 weeks later...
Hebert Leandro

Nice work man. In my pc program close on "Performance" tab and show "Whoops" kkkkkkkk.Others it work. 

 

Windows 7 (x64) SP1

Intel i7 950 Bloomfield 1366

Gigabyte ga-x58a-ud3r

G.skil 2x 4GB Dual Channel XMP@1600

Geforce GTX 680 @ SLI

XFX Pro 650W 

 

 

Update! August 06  2014  

 

This version works for me.

Thanks again.

Link to post
Share on other sites
  • 3 months later...
Zero3K

It would be nice if you added the ability to have it replace the default task manager and implemented double buffering to the UI so it won't flicker anymore.

Link to post
Share on other sites
  • 1 month later...
  • 3 months later...
Ismo69

How am I supposed to download that? Clicking the link only throws me up on the page.

Link to post
Share on other sites
zhangm

How am I supposed to download that? Clicking the link only throws me up on the page.

Try the link in the above post again.

Alternatively, the URL remains valid. You can copy and paste it into your browser manually.

http://dbcstudio.net/software/download/dbctaskman/links.html

 

Link to post
Share on other sites
  • 4 weeks later...
  • 1 month later...
Thomas the Tank Engine

Is this still getting worked on, because the last update & any movement on this app was in May of 2015?

Link to post
Share on other sites
  • 1 month later...
JohnnyXP64

if you disable the cache file for a DISK, and work without a pageFile, the task manager crashes with a mgbox "Whoops"

Link to post
Share on other sites
BinaryData

Hmm.. Will this still be good if Microsoft forces everyone to upgrade to 10?

Link to post
Share on other sites
  • 3 weeks later...
wmbfpz

Hi this looks perfect - I downloaded from the links page.However when I unzipped and ran it I got the Whoops message. 

 

I note a number of times that this has happened in the past - is there a fix or a later version that fixes this.

 

Is there a fix for this dll required or do I need to copy it to a windows system dir in order for it to work?

 

I've tried a few dirs with no improvement.

 

Is it possible to obtain a prior version?

 

Many thanks for all your great work

Link to post
Share on other sites
  • 4 months later...
alexp5

Hi there, it would be great replacement for WIn 7 if act same way as WIn 7 original task manager does, find one think, but maybe I missed something. 

When you go to process in original WIn 7 task manager you can choose for svchost service in properties and that jumps in HIGHLIGHTED lines in Service screen what service is using that 

In your does almost same, when you are in details and when jumps to services screen I just see screen without any highlights so basically useless when comes to read svchost service activity. 

Maybe that does just for me - Win 7 Ultimate, 86x

Link to post
Share on other sites
  • 8 months later...
  • Skiver locked this topic
This topic is now closed to further replies.
  • Recently Browsing   0 members

    No registered users viewing this page.

  • Similar Content

    • By indospot
      Patch Tuesday: Here's what's new for Windows 8.1 and 7 this month
      by João Carrasqueira



      We're 13 days into October, but it's not truly a new month until Microsoft releases its Patch Tuesday updates for Windows, and as we're on the second Tuesday of the month, that happens today. Along with all supported versions of Windows 10, there are also new cumulative updates rolling out to Windows 8.1 and some Windows 7 users.

      There are two kinds of updates for each operating system - the monthly rollup update and the security-only update. For Windows 8.1, the monthly rollup update is KB4580347 and you can download it manually here. It includes the following changes:

      It also has a couple of known issues:

      Symptom Workaround Certain operations, such as rename, that you perform on files or folders that are on a Cluster Shared Volume (CSV) may fail with the error, “STATUS_BAD_IMPERSONATION_LEVEL (0xC00000A5)”. This occurs when you perform the operation on a CSV owner node from a process that doesn’t have administrator privilege. Do one of the following:

      Perform the operation from a process that has administrator privilege. Perform the operation from a node that doesn’t have CSV ownership. Microsoft is working on a resolution and will provide an update in an upcoming release.

      When installing a third-party driver, you might receive the error, “Windows can’t verify the publisher of this driver software”. You may also see the error “No signature was present in the subject” when attempting to view the signature properties using Windows Explorer. This issue occurs when an improperly formatted catalog file is identified during validation by Windows. Starting with this release, Windows will require the validity of DER encoded PKCS#7 content in catalog files. Catalogs files must be signed per section 11.6 of describing DER-encoding for SET OF members in X.690.

      If this happens, you should contact the driver vendor or device manufacturer (OEM) and ask them for an updated driver to correct the issue.

      As for the security-only update, it's KB4580358 and you can download it manually here. It only includes the first and last of the bullet points from the monthly rollup. It also has the same known issues as the monthly rollup.

      Of course, for Windows 7, only certain businesses can legitimately obtain the updates, since you need to be paying for extended security updates (ESU) after Microsoft dropped extended support for the operating system at the start of the year. The monthly rollup here is KB4580345, and you can download it manually here. It includes the following changes:

      The update has one known issue:

      Symptom Workaround Certain operations, such as rename, that you perform on files or folders that are on a Cluster Shared Volume (CSV) may fail with the error, “STATUS_BAD_IMPERSONATION_LEVEL (0xC00000A5)”. This occurs when you perform the operation on a CSV owner node from a process that doesn’t have administrator privilege. Do one of the following:

      Perform the operation from a process that has administrator privilege. Perform the operation from a node that doesn’t have CSV ownership. Microsoft is working on a resolution and will provide an update in an upcoming release.

      The security-only update here is KB4580387 and you can get it manually here. It includes the same changes as the monthly rollup, except the third and fourth bullet points. It also has the same known issue.

      As usual, the monthly rollup updates should install automatically sooner or later, but if you want the security-only updates, you'll need to install them manually from the links above.

    • By Rich Woods
      Office 2010 and Office 2016 for Mac reach their end of life
      by Rich Woods



      Today is Patch Tuesday, and that means that some of Microsoft's products are nearing the end of support. It happens every single month. As Microsoft confirmed in a blog post, Office 2010 is getting its final updates today, as is Office 2016 for Mac.

      The firm also reiterated that you'll need Office 2016 (for Windows), Office 2019, or Microsoft 365 Apps in order to connect to services like Exchange and SharePoint Online. Obviously, Microsoft wants users to switch to Microsoft 365. Office 2010 and Office 2016 for Mac are perpetual license products, meaning that you own them forever. Indeed, after today, they're no longer supported, but you can use them for as long as you want, albeit in an insecure state. Microsoft 365 is obviously a subscription product that keeps you paying if you want to use it.

      Speaking of keeping yourself updated, there are some end of life dates for Windows 10 coming up as well. First up is version 1809, which will no longer be supported after next month. In fact, support for Windows 10 version 1809 was extended due to the COVID-19 pandemic. Because of that, support for version 1903 is also coming to an end soon, but that one will be in December.

    • By indospot
      Here's what's new for Windows 8.1 and 7 this Patch Tuesday
      by João Carrasqueira



      We are now in the second Tuesday of September, and in usual Microsoft fashion, that means it's Patch Tuesday. Every supported version of Windows is getting updates today, and that includes Windows 8.1. Plus, if you're paying for extended security updates (ESU), there are new updates for Windows 7, too.

      As usual, there are two flavors of the monthly updates, one containing only security fixes and one with other quality fixes, the monthly rollup update.

      For Windows 8.1, the monthly rollup is KB4577066, and it can be downloaded manually here. It contains the following fixes:

      It also has a single known issue that's been around for months:

      Symptom Workaround Certain operations, such as rename, that you perform on files or folders that are on a Cluster Shared Volume (CSV) may fail with the error, “STATUS_BAD_IMPERSONATION_LEVEL (0xC00000A5)”. This occurs when you perform the operation on a CSV owner node from a process that doesn’t have administrator privilege. Do one of the following:

      Perform the operation from a process that has administrator privilege. Perform the operation from a node that doesn’t have CSV ownership. Microsoft is working on a resolution and will provide an update in an upcoming release.

      As for the security-only update, it's KB4577071, and it can be downloaded manually here. It only includes these updates:

      It has the same known issue as the monthly rollup.

      As for Windows 7, which - again - is only getting updates for paying ESU customers, the monthly rollup update is KB4577051, and it can be downloaded manually here. Here's what's changed:

      The only known issue is the same as for Windows 8.1. Microsoft also notes that the update will fail to install if you don't have a valid key to receive security updates beyond the original end of support date.

      As for the security-only update, it's KB4577053, and it can be downloaded manually here. It contains these changes:

      It has the same known issue mentioned above.

      As a reminder, the quality updates are usually automatically installed through Windows Update, but you'll need to download the security-only updates manually if you want them.

    • By Infernoprince
      Hi all,

      I'm running windows 7 x64.

      The BSOD occured after I used a program called driver hub to update my drivers. It was going well, however after attempting to download a driver (I believe it had to do with a USB driver but I can't confirm) my computer shutdown. I restarted the computer and tried to reinstall the driver, I also got a prompt to update windows so I did that as well. My computer shutdown again but this time it loaded into a BSOD.

      I've tried to boot into safe mode and it starts loading drivers but then stops and shuts down. I tried to use last know good configuration but that didn't work either. I tried to load into automatic repair mode but that didn't work, and system restore doesn't work either. I do however have access to command prompt, windows memory diagnostics, and system image recovery (although it says windows cannot find a system image on this computer)

      Technical Information on blue screen:

      *** STOP: 0x0000007E (0xFFFFFFFF80000003, 0xFFFFF8800194A02D, 0xFFFFF880009A9468, 0xFFFFF880009A8CD0)

      *** asstahci64.sys - Address FFFFF8800194A02D base at FFFFF88001934000, Datestamp 599a919f
      ------------------------------------------------------------
      Information from startup repair
      Problem signature:
      Problem Event Name: StartupRepairOffline
      Problem Signature 01: 6.1.7600.16385
      Problem Signature 02: 6.1.7600.16385
      Problem Signature 03: unknown
      Problem Signature 04: 21198527
      Problem Signature 05: AutoFailover
      Problem Signature 06: 11
      Problem Signature 07: 0x1000007e
      OS Version: 6.1.7601.2.1.0.256.1
      Locale ID: 1033

      ---------------------------------------------------
      Diagnosis and repair details:
      ---------------------------------------------------
      Root cause found:
      ---------------------------------------------------
      Unknown Bugcheck: Bugcheck 1000007e. Parameters = 0xffffffff80000003, 0xfffff8800ad8502d, 0xfffff880033dfec8, 0xfffff880033df730.

      Repair action: System files integrity check and repair
      Result: Failed. Error code = 0x490
      Time taken = 136422 ms
      ---------------------------------------------------
      Session details
      ---------------------------------------------------
      System Disk = \Device\Harddisk0
      Windows directory = D:\Windows
      AutoChk Run = no
      Number of root causes = 1

      Ask me if you need any other information.
    • By Usama Jawad96
      Microsoft apparently just fixed a Windows security flaw first reported to it in 2018
      by Usama Jawad

      Microsoft fixed quite a number of bugs in this month's Patch Tuesday update, which came out last week. While it packed numerous fixes for various versions of Windows, it did draw some criticism for the handling of a security vulnerability that was reported to it by Google.

      However, it appears that the Redmond giant's security woes are not yet over as a new report claims that the firm just fixed a Windows zero-day exploit that was reported to it back in 2018.



      Last week, Microsoft fixed a security hole in various versions of Windows that mainly deals with the operating system's incorrect handling of file signatures. In CVE-2020-1464, the company noted that:

      In a blog post on Medium, security researcher Tal Be'ery has explained that Bernardo Quintero, a manager at VirusTotal - a service owned by Google - first discovered the vulnerability being exploited back in August 2018. This exploit, internally called "GlueBall", was immediately reported to Microsoft and the findings were published in January 2019 by Quintero. Microsoft acknowledged the issue and added mitigation actions in supporting tools, but stated that it would not fix the issue in the operating system itself. The reasoning behind this decision is not public.

      After this, several blog posts were published by other people, explaining how to use GlueBall to exploit Windows. Then in June 2020, GlueBall was once again highlighted by prominent social media accounts.

      It would seem that roughly around this time, Microsoft began to take this issue seriously and a proper fix to the gaping security hole was finally released in this month's Patch Tuesday. According to Microsoft's security advisory, this flaw was present in Windows 7, 8, 8.1, RT 8.1, Server 2008, 2012, 2016, 2019, and Windows 10, going all the way up to version 2004, and that it was exploited across numerous versions of the operating system.

      In a vague statement to KrebsonSecurity, Microsoft stated that:

      The handling of this incident from Microsoft's end is extremely strange, to say the least. One has to wonder why Microsoft delayed fixing a Windows security flaw for nearly two years, especially when it was present in virtually all major versions of the operating system.

      Source: Tal Be'ery (Medium) via KrebsonSecurity