Afrikaans
Akan
Albanian
Amharic
Armenian
Azerbaijani
Basque
Belarusian
Bemba
Bengali
Bihari
Bosnian
Breton
Bulgarian
Cambodian
Catalan
Cebuano
Cherokee
Chichewa
Chinese (Simplified)
Chinese (Traditional)
Corsican
Croatian
Czech
Danish
Dutch
English
Esperanto
Estonian
Ewe
Faroese
Filipino
Finnish
French
Frisian
Ga
Galician
Georgian
German
Greek
Guarani
Gujarati
Haitian Creole
Hausa
Hawaiian
Hebrew
Hindi
Hmong
Hungarian
Icelandic
Igbo
Indonesian
Interlingua
Irish
Italian
Japanese
Javanese
Kannada
Kazakh
Kinyarwanda
Kirundi
Kongo
Korean
Krio (Sierra Leone)
Kurdish
Kurdish (Soranรฎ)
Kyrgyz
Laothian
Latin
Latvian
Lingala
Lithuanian
Lozi
Luganda
Luo
Luxembourgish
Macedonian
Malagasy
Malay
Malayalam
Maltese
Maori
Marathi
Mauritian Creole
Moldavian
Mongolian
Myanmar (Burmese)
Montenegrin
Nepali
Nigerian Pidgin
Northern Sotho
Norwegian
Norwegian (Nynorsk)
Occitan
Oriya
Oromo
Pashto
Persian
Polish
Portuguese (Brazil)
Portuguese (Portugal)
Punjabi
Quechua
Romanian
Romansh
Runyakitara
Russian
Samoan
Scots Gaelic
Serbian
Serbo-Croatian
Sesotho
Setswana
Seychellois Creole
Shona
Sindhi
Sinhalese
Slovak
Slovenian
Somali
Spanish
Spanish (Latin American)
Sundanese
Swahili
Swedish
Tajik
Tamil
Tatar
Telugu
Thai
Tigrinya
Tonga
Tshiluba
Tumbuka
Turkish
Turkmen
Twi
Uighur
Ukrainian
Urdu
Uzbek
Vietnamese
Welsh
Wolof
Xhosa
Yiddish
Yoruba
Zulu
We've asked some great questions
to understand our problem.
We've isolated our problem to
an effective area and looked at our cookie crumbs.
Now it's time to start fixing the issue.
In the IT world,
as in life, problems,
don't always have one right answer.
When you troubleshoot an issue,
you're essentially trying to
isolate it to the root cause.
To help you isolate an issue,
you need to try some remediation steps.
If they don't work, then you can rule those out
as the cause. What's next?
Here's where the start with
the quickest step first method comes into play.
We want to get to a root cause effectively.
But sometimes there are multiple options
we can use to isolate something.
How do we know which option to try first?
It's pretty simple. Try whatever is fastest first.
I'm having a really weird issue with my software.
When I start it. It doesn't do
anything and I just installed it.
Interesting. You know it might've
gotten corrupted during installation.
Let's re-install it again.
It still does the same thing.
I'm having a really weird issue with my software.
When I start it it doesn't do anything.
I just installed it.
Do you have to remember if you restarted
the computer when you installed it.
It works now.
It's possible that in this scenario,
a software reinstall could fix the issue.
It's also possible that a restart was the solution.
Since you can test a restart faster than a reinstall,
you should test the restart first.
You want to be able to troubleshoot and resolve
issues effectively and efficiently.
Remember to start with the quickest step first,
your time and your users time are important.
Can't find what you're looking for?
Get subtitles in any language from opensubtitles.com, and translate them here.