Identify the E135 configuration first
The May 2014 Western Europe specifications identify ThinkPad Edge E135 machine type 3359 as an AMD platform, with Radeon HD 6310/7340 graphics and Realtek ALC3202 audio in the listed configurations. The nearby E130 type 3358 is an Intel platform. Match the full model instead of assuming these related names share every driver.
Record the installed Windows version and architecture, the affected device name or hardware ID, and the current driver version. The ThinkPad Edge E135 archive is an independent historical reference, not Lenovo’s automatic detection tool. Use Lenovo’s supported-device list and the package README to confirm compatibility. Our model-identification guide explains the identifiers without requiring you to publish a serial number.
Start with the affected device
Wireless disconnections or missing networks
Choose by the fitted adapter. Lenovo DS031807 and its H4WB06WW README include E135 among supported systems and name Broadcom 4313/43228/43142 devices; the README requires checking the model-to-device and model-to-OS mapping. Separately, Realtek RTL8188CE document DS031805 has an E135 footnote limiting its listed support to Windows 8 64-bit. These examples do not justify prescribing Intel 2230 to every E135 or assuming every package fits every Windows version.
Check Wi-Fi and airplane-mode controls available in the installed OS, and test whether another device can connect to the same network. If a recent update caused the fault, inspect the adapter’s available rollback option. Save the correctly matched installer offline before uninstalling anything.
Microsoft’s Wi-Fi guidance puts full Network reset after simpler checks and driver troubleshooting; VPN or virtual-network configuration may need to be restored afterward. For a sleep-related disconnect, test the adapter’s Power Management setting only if present, record the original value and restore it if unhelpful. Reduced power saving can increase battery use.
Touchpad or pointer problems
Synaptics is a verified E135 association: DS104313 and the HSG201WW README list the E135, version 19.0.12.61 and Windows 10 32/64-bit. The instructions allow an overwrite update, followed by a restart. The separate uninstall instructions, including utility removal, apply when deliberately uninstalling; they are not a requirement to remove everything before an ordinary update.
Check the device’s enabled-state and sensitivity settings before reinstalling. Note whether the problem began after an update or occurs only in one application. Use the matched package’s documented update method and restart requirements, rather than removing unrelated keyboard or HID devices.
No sound or microphone input
Use the actual Realtek device and OS match rather than the Conexant 20671 recommendation. Lenovo DS031916 and the H4AS09WW README include E135 with Realtek High Definition Audio 6.0.1.6909. Its current OS list names Windows 8 and Windows 10, 32/64-bit; Windows 8.1 appears in older change-history entries but was later removed. Follow the current applicability list and normal overwrite/restart instructions, not a blanket complete-removal rule.
Before changing software, check the selected playback/recording device, mute state, connections and whether the problem affects one application or the whole system. Microsoft’s audio guide separates these checks from driver and service troubleshooting. Follow the applicable OS section; its presence does not establish manufacturer support for every OS on the E135.
Graphics, USB or battery symptoms
For flicker after a driver change, compare the symptom before and after a rollback when available. Microsoft’s flicker checks help distinguish a likely driver fault from an incompatible app on covered Windows versions. Select the actual graphics device and exact model’s package; routine DDU or third-party driver cleaning is not the first installation step.
For USB trouble, note which port and device fail and test a known-working cable or peripheral before assuming all USB drivers are wrong. For charging or short runtime, check the adapter, battery health and power use. Lenovo’s Battery Q&A explains that gauge calibration improves an inaccurate estimate, not lost battery capacity.
Change one relevant package at a time
- Read the package’s model, device, OS, architecture and prerequisite sections. A higher version number is not proof of compatibility.
- Back up important files and keep a copy of the prior working installer. A restore point can help with some system changes, but System Restore is not a backup of personal files and can change installed applications and drivers.
- Follow the package’s actual installation order and uninstall conditions. Do not apply one generic chipset/storage/graphics order to every repair.
- Restart when instructed, check the installed version and repeat the original failing task. Record the result before changing another device.
Device Manager’s update, rollback and reinstall procedures are different operations. Windows attempts to reinstall an uninstalled driver; keep an offline fallback in case it does not. Review relevant security or corrective updates instead of changing every driver on a monthly schedule.
Use targeted recovery, not routine cleaning
The reviewed E135 BIOS document DS031727 and HMUJ10WW README identify BIOS 2.58 / HMET98WW. They do not establish that a BIOS update routinely fixes a touchpad fault. The README recommends USB 3.0 driver 1.4.0.225 or later before the BIOS update, requires AC plus a charged battery, and warns that BIOS 2.52 or later cannot be rolled back below 2.52. Its Windows utility lists Windows 8/7 and XP Professional SP3; a Windows 10 audio or touchpad package does not expand that utility’s OS scope.
Read the full firmware prerequisites and version-specific procedure before considering a flash. Record existing settings, including SATA mode, because settings can reset. Back up data, keep your BitLocker recovery key accessible if encryption is enabled, and do not power off or suspend during the update. Ask qualified support when the required update path is unclear.
Routine registry cleaning is not a driver-maintenance requirement. Microsoft warns that incorrect registry changes can cause serious problems. If an applicable official fix requires a specific edit, first follow the registry backup guidance and preserve a recovery route. A vague recommendation to clean the registry is not such a fix.
If the fault persists, provide Lenovo support or a qualified technician with the full model, installed OS, device identifier, driver version, error message and tests already tried. Avoid expanding an unresolved problem into repeated full-driver removals or unrelated firmware changes.
Official documentation and linked site destinations checked on October 2, 2026. Historical packages describe their own compatibility scope; availability does not establish ongoing support for an operating system.