BUG: IGSDS Service writes runaway log file (igsds_log_Integrated.txt) consuming 300+ GB on Intel Cor

[CTA1723]

BUG: IGSDS Service writes runaway log file (igsds_log_Integrated.txt) consuming 300+ GB on Intel Core Ultra Series 2 systems

Summary

The IGSDSserviceIntegrated service writes to C:\ProgramData\Intel\IGSDS\igsds_log_Integrated.txt continuously, with no log rotation, truncation, or size limit. The file grows several gigabytes per hour and eventually exhausts disk space, taking machines out of commission. Confirmed on 14 Intel Core Ultra Series 2 business endpoints with Intel Arc 130V integrated graphics — despite the Intel Precompiled Shader Distribution feature being disabled by default and never manually enabled on any affected machine.

Environment

• Hardware: Intel Core Ultra Series 2 (Lunar Lake) with Intel Arc 130V GPU (8GB) integrated graphics
• OS: Windows 11
• Driver: Intel Graphics Driver 32.0.101.8509 (WHQL, released February 13, 2026)
  • Specifically the Dell-shipped OEM build: Intel-Graphics-Driver_DHT41_WIN64_32.0.101.8509_A01_01.EXE
• Driver date: 02/04/2026
• Feature status: Intel Precompiled Shader Distribution is in its default DISABLED state on every affected machine; no user enabled it

Timeline Anomaly

This driver (32.0.101.8509) was released February 13, 2026 — but Intel's public release notes for this version make no mention of the Intel Graphics Shader Distribution Service. The feature wasn't officially announced until driver 32.0.101.8626 on March 17, 2026, roughly a month later.

This means the IGSDS service was shipping silently in 8509 before the feature was publicly documented. Affected administrators have no easy way to identify the service as the cause because it doesn't appear in the release notes for the driver they're actually running.

Observed Behavior

• Log file C:\ProgramData\Intel\IGSDS\igsds_log_Integrated.txt grows continuously after driver installation
• Measured growth rate: ~4 GB per 15 minutes (~16 GB/hour) on one actively-monitored machine
• No log rotation, truncation, or size cap enforced
• Log continues to grow even though the gaming feature it supports is disabled
• On a two-week-old laptop, the log had reached 339 GB
• Affected machines eventually hit 99.9% disk full state, causing OS-level instability and write failures

Fleet Impact (14 Confirmed Affected Machines)

Log sizes at time of remediation:

Machine Log Size

Machine A	392.51 GB
Machine B	357.75 GB
Machine C	347.59 GB
Machine D	337.15 GB
Machine E	318.35 GB
Machine F	316.82 GB
Machine G	315.63 GB
Machine H	~280 GB
Machine I	277.02 GB
Machine J	255.90 GB
Machine K	196.13 GB
Machine L	176.99 GB
Machine M	168.63 GB
Machine N	99.05 GB

Total disk space recovered after remediation: ~3 TB

Two additional machines were offline during remediation runs and not included in the above count, but are likely affected based on their last-known state.

Related Components

• Service: IGSDSserviceIntegrated
• Parent service: IntelGraphicsSoftwareService
• Process writing the log: igfxShaderDistributionService.exe (located in C:\Windows\System32\DriverStore\FileRepository\iigd_dch.inf_amd64_*\)
• Related AppX package: AppUp.IntelArcSoftware

Reproduction Steps

1. Install Intel Graphics Driver 32.0.101.8509 (or any of the subsequent versions that contain IGSDS) on an Intel Core Ultra Series 2 system with integrated Arc graphics
2. Do NOT enable Intel Precompiled Shader Distribution in Intel Graphics Software (leave at default disabled state)
3. Use the machine normally
4. The log file grows without bound

Critical Concern

The feature is disabled by default and explicitly documented as requiring manual user enable to take effect. Yet the supporting service continues to write to disk regardless of feature state. This means:

• Business endpoints, kiosks, and any environment where users never interact with Intel Graphics Software are affected
• Users get zero functional benefit from the logging
• The bug is most severe in environments least likely to detect it (no gaming workload, no reason to look in ProgramData\Intel)

Workaround (Verified, Survives Reboots)

The following PowerShell sequence recovers disk space, prevents recurrence, and has been confirmed to survive at least one reboot cycle:

# 1. Kill the processes writing the log
Get-Process | Where-Object { $_.Name -match "(?i)igfxShader|IntelGraphicsSoftware" } |
    Stop-Process -Force

# 2. Stop and disable the related services
Get-Service | Where-Object { $_.Name -match "(?i)IGSDSservice|IntelGraphicsSoftwareService" } |
    ForEach-Object {
        Stop-Service -Name $_.Name -Force -ErrorAction SilentlyContinue
        Set-Service -Name $_.Name -StartupType Disabled
    }

# 3. Delete the log file
Remove-Item "C:\ProgramData\Intel\IGSDS\igsds_log_Integrated.txt" -Force

This is a workaround, not a fix. Subsequent Intel graphics driver updates may reinstate the services. We have not observed any negative impact on graphics functionality, display output, or productivity applications after disabling these services — the actual GPU driver in the DriverStore is unaffected.

Note: Driver versions 32.0.101.8626 (March 17, 2026), 32.0.101.8629 (April 7, 2026), and 32.0.101.8737 (April 29 / May 2, 2026) have all been released since 8509 but none mention any fix for this issue in their release notes. Updating to a newer driver does not appear to resolve the bug.

Requests

1. Acknowledge the bug publicly so administrators know to look for it
2. Implement log rotation and size limits on igsds_log_Integrated.txt (a reasonable cap such as 100 MB with rolling rotation would prevent this category of issue entirely)
3. Suppress logging when the feature is disabled — the service should not be generating gigabytes of log data for a feature the user has not enabled
4. Document the service in release notes for driver versions that contain it, particularly retroactively for 32.0.101.8509 where the service shipped silently
5. Provide a documented enterprise mechanism to disable IGSDS (Group Policy, registry key, or installer flag) for environments where the feature provides no value

For Other Administrators Finding This Report

If you're experiencing the same issue, you can identify affected machines by checking the size of C:\ProgramData\Intel\IGSDS\igsds_log_Integrated.txt. The PowerShell workaround above can be deployed via any endpoint management solution and has been validated across 14 machines without negative impact on graphics functionality.

Happy to provide additional diagnostic data, full PowerShell remediation scripts, or coordinate with Intel support staff on reproduction.

[Mike_Intel]

Hello CTA1723,

Thank you for posting in Intel community Forum.

For me to better understand and diagnose the issue further, let me ask you to provide detailed responses to the following questions. This information will help me isolate the problem and determine the most appropriate course of action moving forward.

1. When did you start having this issue or how did you notice the issue?
2. Aside from the workaround that you mentioned, can you also provide other troubleshooting steps that you tried for me to document.
3. Aside from OEM Driver version 32.0.101.8509, have you also tried another driver version from OEM or from Intel?
4. Can you share some screenshots of the issue?
5. For me to review the hardware and the driver installed, please help generate the SSU logs of your system. Kindly refer to the link below for the steps:

How to get the Intel® System Support Utility Logs on Windows*

If you have questions, please let us know. Thank you.

Best regards,

Michael L.

Intel Customer Support Technician

[RAM4854]

so is a fix in process for this, I have several machines in my enterprise that are going through the same thing, the workaround is working and so far no more log files issues on the machines that I ran a powershell script I made. 

Please provide an update when possible on the permanent resolution for this. thank you.. 

[Devin4]

I have this same exact issue. This has completely choked up my PC - the igsds_log_integrated.txt file is over 700GB! Under C:/ProgramData/Intel/IGSDS

[Mike_Intel]

Hello CTA1723,

I hope this message finds you well. 

Were you able to check the previous post?

If you have questions, please let us know. Thank you.

@Devin4

If you need assistance, please create a new thread for us to assist you on your own thread and gather the details of your systems.

Best regards,

Michael L.

Intel Customer Support Technician

[Devin4]

Why should I create a new thread when I'm having the exact same issue as described by the creator of this thread? Have you done anything to resolve the issue? You provided no actual solution to his very detailed post.

[gl444]

I'm having this exact same problem on a handful of new laptops with the Intel Ultra 7 268V processor with the Intel Arc 140V integrated GPU.

[Mike_Intel]

Hello CTA1723,

I hope you are having a good day.

I am sending another follow up on the information that I requested. 

Since we have not heard back from you, I need to close this inquiry. 

If you need further assistance, please post a new question as this thread will no longer be monitored. 

Thank you and have a great day. 

@RAM4854 and @gl444

If you need assistance, please create a new thread for us to assist you on your own thread and gather the details of your systems.

Best regards,

Michael L.

Intel Customer Support Technician