Quick wins for a faster PC:
Clear out junk files and repair common Windows errorsFree Scan →Fix the driver behind crashes, sound loss and screen glitchesFind Drivers →Open the Command Palette and run Developer: Show Running Extensions. Start its profiler, then reproduce the exact lag you are investigating. The view shows which active extensions consume time in that captured workload. If that produces only a lead, run Help: Start Extension Bisect to disable groups and narrow the candidates. An Empty Profile or the --disable-extensions command-line option can establish whether extensions or customized settings are involved, but neither one names a culprit by itself.
Start with the symptom you can reproduce
“VS Code feels slow” is too broad for a reliable diagnosis. First decide what actually becomes slow: opening the application, opening a particular workspace, switching files, typing, code completion, saving, searching, formatting, debugging, or another action. A startup delay and typing lag can have different causes, and a profile captured during one cannot be treated as evidence about the other.
As an Amazon Associate I earn from qualifying purchases.
Keep the test conditions stable. Use the same VS Code window, workspace, files, language mode, and action each time. If the problem happens only in one repository, do not compare it with an empty folder. If it appears only after a file grows large, use a similarly sized file during every comparison. Write down the exact sequence that triggers the delay and whether the delay is constant or intermittent.
Do these 3 things before closing this tab:
1Repair Windows errors before they cause bigger problems2Scan for outdated or missing drivers - takes under a minute3Clear out junk files and repair common Windows errors- Record whether the issue is startup-time or occurs after the editor is ready.
- Note the workspace type: local folder, Remote SSH, WSL, container, Codespaces, or browser-based VS Code.
- Capture the VS Code version and the extension versions installed when you test.
- Decide what counts as “bad” before bisecting, such as a completion popup taking several seconds or keystrokes appearing late.
Use Running Extensions to obtain a performance lead
The built-in Running Extensions view is the fastest first check because it measures extensions while they are active. Microsoft describes its profiling feature as a way to identify extensions that take the most time. That measurement belongs to the workload you capture; it is not a permanent ranking of extensions for every project or computer.
#1 Best Overall
- [Ultra-Lightweight Ear Buds Designed for Small Ears] Each earbud weighs only 3.7g and features a compact, ergonomic in-ear design made especially for small ears. Secure, low-profile, and comfortable for workouts, all-day wear or overnight sleeping.The ultra-slim profile sits flush in your ear with no hard edges poking or rubbing, so you can even sleep on your side without discomfort.
- [Immersive Stereo Sound with TOZO OrigX Technology] TOZO OrigX tuning delivers clear vocals, balanced mids, and natural stereo sound for music, podcasts, and videos.
- [Long Battery Life for Daily Use] Get up to 7 hours of playtime on a single charge, with up to 32 hours total using the charging case—ideal for workdays, commuting, and extended listening sessions.
- [Bluetooth 5.3 & Stable Connection] Bluetooth 5.3 provides fast pairing, stable wireless performance, and reduced dropouts as you move around home or office.
- [Deep Bass with Clear Vocals] High-performance drivers produce punchy bass while keeping vocals clean and detailed for everyday listening.
Profile the affected action
- Open the Command Palette with
Ctrl+Shift+Pon Windows or Linux, orCmd+Shift+Pon macOS. - Run Developer: Show Running Extensions.
- In the Running Extensions editor, start the available profiling command or control.
- Perform the same action that causes the slowdown. For typing lag, type in the same file and trigger the same completion or validation behavior. For startup, restart the window and capture the startup sequence instead.
- Stop the profile after the symptom has occurred and inspect the reported extension times.
Look for extensions that consume substantial time during the captured interval, especially when their activity lines up with the moment you notice the lag. Treat that extension as a candidate for confirmation, not as proven guilty. An extension can appear busy because your workload legitimately invokes it, and another component can still be responsible for the visible delay.
Interpret the result in context
A startup profile answers a startup question. A profile taken while you type answers a question about that editing workload. Do not use a high startup value to claim that the same extension causes completion lag unless you reproduce and profile completion lag separately.
VS Code runs extensions in extension hosts. Depending on your setup, a host can be local, web-based, or remote. A remote workspace may involve more than one host, so the location shown for an extension is useful context rather than a universal attribution rule. Diagnose from the affected window and workspace, not from a second local window that uses a different host.
Narrow the cause with Extension Bisect
When the slowdown is repeatable but Running Extensions leaves several candidates, use Help: Start Extension Bisect. VS Code disables extensions in groups, asks whether the problem remains, and uses your answers to select the next group. Continue until the candidate set is small enough to test individually.
Run a controlled bisect
- Open the Command Palette and run Help: Start Extension Bisect.
- Allow VS Code to restart or reload with a subset of extensions disabled, following the prompts.
- Reproduce the same symptom using the same workspace and action you documented earlier.
- Choose Good now when the problem has disappeared, or This is bad when it is still present.
- Repeat each round until VS Code identifies a likely extension. If the result is unclear, restart the bisect and make the test conditions more consistent.
Your answers are the data the algorithm uses. If the problem occurs only occasionally, or if you change files and actions between rounds, a “good” answer may be a lucky run rather than evidence that the disabled group contained the cause. Wait for the same trigger and judge each round against the same threshold.
Rank #2
- 【IP68 Waterproof Multifunctinal Smart Watch】Torjalph fitness activity tracker smart watch is IP68 waterproof technology ,you can wear it when swimming,handwashing,it's rain-proof which means that you perform multiple exercise modes outside without worrying about sweat or rain corroding your fitness smart watch,and this watch equipped with a 230 mAh large capacity battery magnetic charging ,and this sports activity tracker watch can be used 5-7 days If fully charged.
- 【Larger 1.83'' Full Screen Watch & Multi-dial Selection】1.83 inch full HD color touch screen smart watch for men / women provides excellent 240*284 resolution image quality ,This Bluetooth smart watch offers a better touch experience and remarkable immersion and ,more than 200 watch faces for you to choose from App"Da Fit ", you can change the dial style according to your mood to wear keeping the world on your wrist
- 【Accurate Activity Tracker Smart Watch 】sports watch activity tracker uses sweat and dust resistant breathable silicone strap, our Fitness Tracker Smart Watch for Android iOS Phones supports 12 sports modes,walking,running,bicycle,swimming,badminton,basketball,football,rope skipping. This bluetooth calls smart watch for men women is lightweight and stylish, bringing more convenient and relaxing sports experience while also providing more protection.
- 【Your 24 Hour Personal Daily Health Monitor】Fitness watch for women men full touch screen IP67 waterproof bluetooth smartwatch for Android iOS Phones with heart rate blood pressure monitor multifunction Andriod smart watch with steps counter sleep monitor sports fitness watch, monitoring blood oxygen saturation allows you to understand your physical condition in real time to track fitness progress ,to know your health status in time.
- 【More Functions Bluetooth Call Smart Watch】This fitness activity smart watch full screen for iPhone and Android phones includes a bunch of new features including:The bluetooth smart watch can hang up the phone, receive and display WhatsAPP /Text /Facebook /Twitter /Messenger reminder.Support sedentary reminder, alarm clock, stopwatch, timer,weather information,music control, remote camera control compatible with Android 5.0 and above or iOS 9.0 and above smartphones.
What the algorithm can and cannot promise
Microsoft’s Extension Bisect explanation describes logarithmic behavior, written as average and worst-case O(log N). Its example says that a set of 24 extensions can lead to a result in four or five steps under that example workflow. That is an explanation of the search method, not a guarantee of an exact number of current prompts: reloads, extension dependencies, changing installations, and an inconsistent symptom can alter the interaction.
Bisect tells you that a change in a group correlates with the symptom. After it points to one extension, disable only that extension and reproduce the issue again. This final one-extension check separates a useful lead from a group-level coincidence.
What’s actually slowing this PC down?
Pick the symptom - the matching free tool is one click away.
Test a clean baseline with an Empty Profile
An Empty Profile is useful when you need to know whether customizations are involved at all. VS Code’s profile documentation says this profile disables extensions and modified settings. Create it from the Profiles interface, switch the affected workspace to that profile, and repeat your documented test.
- If the lag disappears, one or more extensions or modified settings in your normal profile are implicated.
- If the lag remains, the cause may be VS Code itself, the workspace, a language service outside the extension set, the remote environment, or another system factor.
- If the lag disappears, the Empty Profile still cannot identify a single extension because it changes two categories at once: extensions and settings.
Use the Empty Profile as a broad branch in the diagnosis, then return to Running Extensions or Extension Bisect to isolate a specific extension. Keep the normal profile unchanged while testing so you can switch back and compare.
Use the command line for a quick isolation check
The VS Code command-line interface provides two useful checks:
Rank #3
- [Low Noise High Fidelity] New bee guitar cord with 22AWG oxygen-free-copper center conductors provides enhanced signal transfer, the PVC insulation material and the high-density stranded copper double shield provide noise rejection for quiet operation
- [Ideal for Choice] New bee 1/4 straight and right angle metal connectors, ensures a secure connection in any instrument, pedal, or amp jack. L shape great fro on stage guitar stands
- [Wide Compatible] Suitable for mixer, power amplifier, microphone, effector, decoder, equalizer, electoronic organ, electric guitar, electric bass and other electronic equipments. Widely used in the installation of smart home, karaoke speaker, professional stage audio, etc
- [Easy Disassemble] Making incidental repairs quick and easy! Very nice, flexible cable
- [Dont Hesite to Order] 24 hours customer services and professional technology team are standing by
code --disable-extensionsThis starts VS Code with all installed extensions disabled. Open the same workspace and perform the same action. If the lag vanishes, extensions matter to the behavior; the command does not identify which one.
Recommended Free Tools
code --list-extensionsThis prints the installed extension identifiers, which is useful for inventory, scripts, and a bug report. It is not a performance measurement. If you need to compare two machines, save the lists alongside their VS Code versions and workspace details rather than assuming identical identifiers mean identical settings or workloads.
When the code command is unavailable, use the command-line launcher supplied by your installation or run the test from a shell where the VS Code command has been installed. Do not remove extensions merely to perform this check; disabling them for one launch preserves your configuration.
Choose the method that matches your question
| Method | Best use | What it tells you | Main limitation |
|---|---|---|---|
| Running Extensions profiling | You need a performance lead while reproducing lag | Which currently running extensions take time in the captured scenario | A measured lead is not proof that the extension causes every slowdown |
| Extension Bisect | The symptom is reproducible and many extensions are installed | Whether disabling groups changes the symptom, progressively narrowing candidates | Inconsistent reproduction or inaccurate answers can produce a false conclusion |
| Empty Profile | You need a clean test of extensions and modified settings together | Whether the problem persists without those customizations | It cannot distinguish one extension from another or from a modified setting |
--disable-extensions |
You want a quick command-line isolation check | Whether disabling every installed extension changes the problem | It provides no per-extension attribution |
A practical sequence is to profile first, bisect second, and use an Empty Profile or the CLI when you need a broad baseline. You do not have to run every method if an earlier, controlled test already answers your question.
Account for local and remote extension hosts
In a local folder, the relevant extension host is normally on your computer. In Remote SSH, WSL, containers, Codespaces, and browser scenarios, extensions can run in different places. An extension installed locally may not be the extension executing against a remote workspace, and an extension installed in the remote environment may not affect a local window.
Free tools Windows power users keep installed
One-click scans. No signup required.
Rank #4
- Digital Family Calendar: BSIMB digital calendar wall touch screen puts an end to your chaotic life. Designed for busy families, the digital calendar keeps you organised and in step with your family. Assign different colours and tasks to each family member to make family scheduling easier and more intuitive.
- Easy Setup and Auto-Sync: Plug in, connect to WLAN and auto-syn your electric calendar in minutes. Digital wall calendar compatible with Google calendar, iCloud calendar, Outlook calendar, Cozi calendar and Yahoo calendar. Add events directly on the device or through the ecalendar app. Electronic calendar stays current whether you're at work or traveling—no manual updates needed.
- All-In-One Home Assistant: Smart calendar builds habits and encourage independence with personalised chores. Display daily meal plan to reduce the daily ‘What's for dinner?’ stress. To-do lists keep track of everything you want. Turning chores into valuable achievements with stars and rewards, making life easier and more enjoyable.
- Manage Anytime Anywhere: BSIMB electronic calendar for family stay connected with the powerful ecalendar app. Access and manage your digital wall calendar anytime, anywhere with free features like stars & rewards, photo screensaver, chore charts, meals plans, to-do lists etc. Electronic planner paid features like Magic Import tailor advanced tools for users with special needs.
- Stay in Touch with Loved Ones: Share photos or videos from your phone to electronic wall calendar with app, instantly update your life moment, and keep in touch with your family, especially those who are far away; you can also surprise your smart calendar digital wall by sending him a wish card; it's also great for keeping tech-illiterate elders in touch with the youngsters.
Open Running Extensions in the window where the lag occurs. Check the host or location information shown for the active extension, and repeat the test after reconnecting if the remote session changes. Keep the remote workspace, connection, and files constant during a bisect; switching between local and remote windows invalidates a direct comparison.
Host location is a clue about where to investigate, not a universal rule that assigns blame. VS Code’s extension-host design separates extension work from the main UI so extensions do not consume unnecessary CPU and memory in the UI process, but an extension can still create visible delays through expensive activation, file watching, language work, or requests that affect the current workflow.
Independent reader supportYour contribution helps us test, update, and keep practical guides available for everyone.Confirm the candidate before changing your setup
Once profiling or bisecting points to an extension, perform a deliberate confirmation:
- Note the exact extension identifier and version from the Extensions view.
- Disable only that extension in the affected window.
- Reload the window if VS Code requests it.
- Repeat the original steps, using the same workspace, file, and action.
- Re-enable the extension and repeat once more if you need to verify that the behavior returns.
A confirmed result should describe a reproducible difference: the symptom occurs with the extension enabled and disappears, or materially improves, when that extension alone is disabled. If disabling it changes nothing, restore it and investigate the next candidate rather than leaving a useful tool disabled on a weak correlation.
Report a reproducible extension issue
If one extension remains the best-supported explanation, give its maintainer enough information to reproduce the case. Include:
- VS Code version and operating system.
- Extension identifier and installed version.
- Whether the window is local, web-based, or connected to Remote SSH, WSL, a container, or Codespaces.
- Workspace type and any important repository or file characteristics.
- Exact steps that trigger the lag and what delay you observe.
- Whether the symptom disappears with that extension disabled.
- A Running Extensions profile or other diagnostic details that can be shared safely.
The VS Code 1.72 release notes describe a Report Issue action in the Running Extensions editor. If that action is present in your version, use it to start the report from the diagnostic context; otherwise, use the extension’s documented issue channel and paste the same reproducible details. Remove proprietary source code, secrets, tokens, and private workspace data before attaching logs or profiles.
Troubleshoot misleading results
The profile names an extension, but disabling it does not help
Repeat the profile during the precise action that feels slow. The extension may have been busy for unrelated work, or the visible delay may come from a different extension, setting, workspace process, or remote service. Confirm with the one-extension disable test before assigning blame.
Bisect reports different answers on different runs
Make the trigger deterministic: use the same file, wait for indexing or connection setup to finish, and perform the same number of edits. Intermittent symptoms can make a group appear “good” by chance. If the problem cannot be reproduced reliably, bisect is less informative than a carefully captured profile and an Empty Profile comparison.
The issue disappears in an Empty Profile
That result identifies the broad category of extensions or modified settings, not a specific extension. Reintroduce changes systematically, or run Extension Bisect with a consistent reproduction while keeping settings unchanged.
The issue remains with every extension disabled
Do not continue blaming extensions without new evidence. Check whether the delay follows one workspace, a remote connection, a particular file size, a language service, or the VS Code version. The all-disabled test establishes only that the installed extensions were not required for the symptom in that run.
Only startup is slow
Capture startup specifically. Do not infer typing or completion performance from a startup profile. Compare startup with the same workspace and connection state, because remote initialization and workspace scanning can change the result.
A repeatable diagnostic checklist
- Describe one observable symptom and define the test action.
- Record workspace, host location, VS Code version, and extension versions.
- Run Developer: Show Running Extensions and profile while the symptom occurs.
- Use Help: Start Extension Bisect if the profile leaves multiple plausible candidates.
- Use an Empty Profile or
code --disable-extensionsfor a broad clean comparison. - Disable the suspected extension alone and repeat the original test.
- Report the reproducible difference with the extension ID, version, environment, and steps.
The reliable answer is therefore not simply the extension with the largest number in a list. It is the extension that remains a reproducible, one-extension difference under the same workload and host context. Built-in profiling supplies the lead; bisecting and controlled disable tests supply the attribution.
Windows Errors? Fix Them Before They Spread
Repair common Windows errors and clear accumulated junk for a smoother, more stable PC - no reinstall needed.Free scan · no reinstallCrashes, No Sound, or Screen Glitches?
Random freezes, missing sound and display glitches usually trace back to one bad driver. Find and replace yours safely.Free scan · under a minuteQuick Recap
Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.
