Jump to content

Search the Community

Showing results for tags 'KB4034679 '.

  • Search By Tags

    Type tags separated by commas.
  • Search By Author

Content Type


Forums

  • The General Stuff
    • Announcements
    • Introduce Yourself!
    • General Discussion
  • Microsoft Software Products
    • Windows 11
    • Windows 10
    • Windows 8
    • Windows 7
    • Windows Server
    • Older Windows NT-Family OSes
    • Windows 9x/ME
    • Other Microsoft Products
  • Unattended Windows Discussion & Support
    • Unattended Windows
    • Other Unattended Projects
  • Member Contributed Projects
    • Nuhi Utilities
    • Member Projects
    • Other Member Contributed Projects
    • Windows Updates Downloader
  • Software, Hardware, Media and Games
    • Forum Categories
    • Mobile Devices
  • Customizing Windows and Graphics
    • Customizing Windows
    • Customizing Graphics
  • Coding, Scripting and Servers
    • Web Development (HTML, Java, PHP, ASP, XML, etc.)
    • Programming (C++, Delphi, VB/VBS, CMD/batch, etc.)
    • Server - Side Help (IIS, Apache, etc.)

Calendars

There are no results to display.


Find results in...

Find results that contain...


Date Created

  • Start

    End


Last Updated

  • Start

    End


Filter by number of...

Joined

  • Start

    End


Group


AIM


MSN


Website URL


ICQ


Yahoo


Jabber


Skype

Found 1 result

  1. Well, the issue reported on Graphics Bug in Windows 7 after installing August 2017 Security Updates, and also by Woody, rather unsurprisingly, also occurs on XP SP3... It only affects those using more than one monitor, and req monitors to be setup in such a way that certain parts of the screen have negative screen positions. For example a secondary monitor setup to the left of the main monitor, or with a higher top border than the main monitor, or both (which is the case of one of my machines). Then the secondary monitor starts acting up. Solution? None, yet, for XP. Workaround: uninstall KB4035055. By doing that the latest win32k.sys (v. 5.1.2600.7312) will be replaced by v. 5.1.2600.7297 (from KB4025877). This issue only happens in the conditions described, everybody using a single monitor, and people using more than one monitor in unaffected spatial arrangementes may safely ignore it and keep the latest win32k,sys! HTH
×
×
  • Create New...