Zwift does not start. There is an error message, which says “Could not find required data files. Closing application now.”. What can I do?
Suggestion: If you are on a Windows PC, check the health of your hard drive. I had a similar error only to find out my hard drive was failing.
I re-mapped the “Documents” folder and it worked again…then there’s the trouble of swapping out a HD.
Yes, it is a Windows machine. SSD works fine. How to re-map that folder?
I had to Google it. I’m sure my explanation would be less effective than what you can find with Google.
Remapped the documents folder but it didn’t help. I also tried to run Zwift as administrator. No change.
[12:23:01] Log Time: 12:23:01 2020-03-29
[12:23:01] Game Version: 1.0.48306
[12:23:01] Config: Shipping
[12:23:01] Launcher Version : 1.0.50
[12:23:01] Loading WAD file 'assets/global.wad' with file.
[12:23:01] ERROR: Could not load wad file: assets/global.wad
[12:23:01] Loading WAD file 'assets/environment/ground/textures.wad' with file.
[12:23:01] ERROR: Could not load wad file: assets/environment/ground/textures.wad
[12:23:01] Loading WAD file 'assets/UI/WhiteOrangeTheme/WhiteOrangeTheme.wad' with file.
[12:23:01] ERROR: Could not load wad file: assets/UI/WhiteOrangeTheme/WhiteOrangeTheme.wad
[12:23:01] Loading WAD file 'assets/UI/minimap/minimap.wad' with file.
[12:23:01] ERROR: Could not load wad file: assets/UI/minimap/minimap.wad
[12:23:01] Loading WAD file 'assets/UI/WhiteOrangeTheme/Scotty/Scotty.wad' with file.
[12:23:01] ERROR: Could not load wad file: assets/UI/WhiteOrangeTheme/Scotty/Scotty.wad
[12:23:01] Loading WAD file 'assets/UI/layouts/layouts.wad' with file.
[12:23:01] ERROR: Could not load wad file: assets/UI/layouts/layouts.wad
[12:23:01] Loading WAD file 'assets/Environment/GrassTextures/GrassTextures.wad' with file.
[12:23:01] ERROR: Could not load wad file: assets/Environment/GrassTextures/GrassTextures.wad
[12:23:01] Successful audio init!
[12:23:01] Loaded audio banks
[12:23:01] Initializing graphics window of size 0 x 0
[12:23:01] Attached Monitors:
[12:23:01] monitor found at: 0,0
[12:23:01] GFX_Initialize: GL_version = 3.1.13586 Compatibility Profile Context FireGL 20.1.2 26.20.15011.10003
[12:23:01] GL_vendor = ATI Technologies Inc.
[12:23:01] GL_render = Radeon Pro 580
[12:23:01] Checking Extensions
[12:23:01] Loading Shader Blur
[12:23:01] ERROR: Missing Vertex Shader asset data/shaders/Final/Blur.vsh
[12:23:01] Calculating Graphics Score
[12:23:01] GFX: Found a vendor/model match for RADEON PRO 580
[12:23:01] Initializing Render Targets
[12:23:01] Initializing Texture Systems
[12:23:01] Calling initialize_zwift_network()
[12:23:01] NETCLIENT:[INFO] CNL 2.5.0
[12:23:01] NETCLIENT:[INFO] Machine Id: 1-91e1a8b3-74bd-4402-b9f1-c7cb04863de3
[12:23:01] Suceeded initializing graphics
[12:23:01] Loading Shader GFXDRAW_NoTexture
[12:23:01] ERROR: Missing Vertex Shader asset data/shaders/Final/GFXDRAW_NoTexture.vsh
[12:23:01] Loading Shader GFXDRAW_Textured
[12:23:01] ERROR: Missing Vertex Shader asset data/shaders/Final/GFXDRAW_Textured.vsh
[12:23:01] Loading Shader GFXDRAW_Textured_Simple
[12:23:01] ERROR: Missing Vertex Shader asset data/shaders/Final/GFXDRAW_Textured_Simple.vsh
[12:23:01] Loading Shader GFXDRAW_Textured_GammaCorrect
[12:23:01] ERROR: Missing Vertex Shader asset data/shaders/Final/GFXDRAW_Textured_GammaCorrect.vsh
[12:23:01] Loading WAD file 'assets/fonts/font.wad' with file.
[12:23:01] ERROR: Could not load wad file: assets/fonts/font.wad
[12:23:01] Using ultra graphics profile
[12:23:01] > res 1920x1080(0x)
[12:23:01] Changed resolution to 1920 x 1080 ( NO MSAA )
[12:23:01] > sres 2048x2048
[12:23:01] Changed shadow resolution to 2048 x 2048
[12:23:01] Syntax Error. USAGE: set VARNAME=VALUE
[12:23:01] Type 'listvars' for list of tweakable variables
[12:23:01] Unknown command "aniso 4"
[12:23:01] > set gSSAO=1
[12:23:01] > set gFXAA=1
[12:23:01] >
[12:23:01] Syntax Error. USAGE: set VARNAME=VALUE
[12:23:01] Type 'listvars' for list of tweakable variables
[12:23:01] OpenGL 3.1.13586 Compatibility Profile Context FireGL 20.1.2 26.20.15011.10003 initialized
[12:23:01] Graphics Vendor: ATI Technologies Inc.
[12:23:01] Graphics Renderer: Radeon Pro 580
[12:23:01] RAM: 40GB
[12:23:01] CPU: Intel(R) Core(TM) i7-7700K CPU @ 4.20GHz
[12:23:01] ANT : ANT USB receiver NOT found
[12:23:01] Loading WAD file 'assets/UI/Achievements/goals.wad' with file.
[12:23:01] ERROR: Could not load wad file: assets/UI/Achievements/goals.wad
[12:23:01] Loading WAD file 'assets/UI/Achievements/achievements.wad' with file.
[12:23:01] ERROR: Could not load wad file: assets/UI/Achievements/achievements.wad
[12:23:01] Streamer: ERROR: #3 Loading XML file "C:\Users\kayki\Documents\Zwift\Zwift_StreamingFiles_ver_cur.xml"!
[12:23:01] Streamer: ERROR: #3 Loading XML file "C:\Users\kayki\Documents\Zwift\Zwift_StreamingFiles_ver_cur.xml"!
[12:23:01] Streamer: ERROR: #3 Loading XML file "C:\Users\kayki\Documents\Zwift\Zwift_StreamingFiles_ver_cur.xml"!
[12:23:01] Registered segment 1 with hash id 888000
[12:23:01] Registered segment 2 with hash id 888001
[12:23:01] Registered segment 3 with hash id 888002
[12:23:01] Registered segment 4 with hash id 888003
[12:23:01] Registered segment 5 with hash id 888004
[12:23:01] Loading Shader GFXDRAW_Textured_ExtAlpha
[12:23:01] ERROR: Missing Vertex Shader asset data/shaders/Final/GFXDRAW_Textured_ExtAlpha.vsh
[12:23:01] Loading Shader SimpleShader
[12:23:01] ERROR: Missing Vertex Shader asset data/shaders/Final/SimpleShader.vsh
[12:23:01] Loading Shader gde_nolighting
[12:23:01] ERROR: Missing Vertex Shader asset data/shaders/Final/gde_nolighting.vsh
[12:23:01] Loading Shader shadowmap
[12:23:01] ERROR: Missing Vertex Shader asset data/shaders/Final/shadowmap.vsh
[12:23:01] Loading Shader shadowmap_instanced
[12:23:01] ERROR: Missing Vertex Shader asset data/shaders/Final/shadowmap_instanced.vsh
[12:23:01] Loading Shader Glossy_shadowmapped
[12:23:01] ERROR: Missing Vertex Shader asset data/shaders/Final/Glossy_shadowmapped.vsh
[12:23:01] Loading Shader Road
[12:23:01] ERROR: Missing Vertex Shader asset data/shaders/Final/Road.vsh
[12:23:01] Loading Shader RoadAccessory
[12:23:01] ERROR: Missing Vertex Shader asset data/shaders/Final/RoadAccessory.vsh
[12:23:01] Loading Shader RoadWet
[12:23:01] ERROR: Missing Vertex Shader asset data/shaders/Final/RoadWet.vsh
[12:23:01] Loading Shader HeatHaze
[12:23:01] ERROR: Missing Vertex Shader asset data/shaders/Final/HeatHaze.vsh
[12:23:01] Loading Shader CausticPass
[12:23:01] ERROR: Missing Vertex Shader asset data/shaders/Final/CausticPass.vsh
[12:23:01] Loading Shader crepuscular
[12:23:01] ERROR: Missing Vertex Shader asset data/shaders/Final/crepuscular.vsh
[12:23:01] Loading Shader SSR
[12:23:01] ERROR: Missing Vertex Shader asset data/shaders/Final/SSR.vsh
[12:23:01] Loading Shader beam
[12:23:01] ERROR: Missing Vertex Shader asset data/shaders/Final/beam.vsh
[12:23:01] Loading Shader beam_inside
[12:23:01] ERROR: Missing Vertex Shader asset data/shaders/Final/beam_inside.vsh
[12:23:01] Loading Shader defaultWorld
[12:23:01] ERROR: Missing Vertex Shader asset data/shaders/Final/defaultWorld.vsh
[12:23:01] Loading Shader defaultWorldAO
[12:23:01] ERROR: Missing Vertex Shader asset data/shaders/Final/defaultWorldAO.vsh
[12:23:01] Loading Shader defaultWorldBillboard
[12:23:01] ERROR: Missing Vertex Shader asset data/shaders/Final/defaultWorldBillboard.vsh
[12:23:01] Loading Shader defaultWorldPhong
[12:23:01] ERROR: Missing Vertex Shader asset data/shaders/Final/defaultWorldPhong.vsh
[12:23:01] Loading Shader defaultWorldSimple
[12:23:01] ERROR: Missing Vertex Shader asset data/shaders/Final/defaultWorldSimple.vsh
[12:23:01] Loading Shader Hologram
[12:23:01] ERROR: Missing Vertex Shader asset data/shaders/Final/Hologram.vsh
[12:23:01] Loading Shader RainbowHologram
[12:23:01] ERROR: Missing Vertex Shader asset data/shaders/Final/RainbowHologram.vsh
[12:23:01] Loading Shader Glossy_locked
[12:23:01] ERROR: Missing Vertex Shader asset data/shaders/Final/Glossy_locked.vsh
[12:23:01] Loading Shader londonTerrainShader
[12:23:01] ERROR: Missing Vertex Shader asset data/shaders/Final/londonTerrainShader.vsh
[12:23:01] Loading Shader londonTerrainShader_HeightMap
[12:23:01] ERROR: Missing Vertex Shader asset data/shaders/Final/londonTerrainShader_HeightMap.vsh
[12:23:01] Loading Shader innsbruckTerrainShader_HeightMap
[12:23:01] ERROR: Missing Vertex Shader asset data/shaders/Final/innsbruckTerrainShader_HeightMap.vsh
[12:23:01] Loading Shader innsbruckTerrainShader
[12:23:01] ERROR: Missing Vertex Shader asset data/shaders/Final/innsbruckTerrainShader.vsh
[12:23:01] Loading Shader bolognaTerrainShader_HeightMap
[12:23:01] ERROR: Missing Vertex Shader asset data/shaders/Final/bolognaTerrainShader_HeightMap.vsh
[12:23:01] Loading Shader bolognaTerrainShader
[12:23:01] ERROR: Missing Vertex Shader asset data/shaders/Final/bolognaTerrainShader.vsh
[12:23:01] Loading Shader yorkshireTerrainShader
[12:23:01] ERROR: Missing Vertex Shader asset data/shaders/Final/yorkshireTerrainShader.vsh
[12:23:01] Loading Shader yorkshireTerrainShader_HeightMap
[12:23:01] ERROR: Missing Vertex Shader asset data/shaders/Final/yorkshireTerrainShader_HeightMap.vsh
[12:23:01] Loading Shader richmondTerrainShader
[12:23:01] ERROR: Missing Vertex Shader asset data/shaders/Final/richmondTerrainShader.vsh
[12:23:01] Loading Shader richmondTerrainShader_HeightMap
[12:23:01] ERROR: Missing Vertex Shader asset data/shaders/Final/richmondTerrainShader_HeightMap.vsh
[12:23:01] Loading Shader WorkoutHologramPortal
[12:23:01] ERROR: Missing Vertex Shader asset data/shaders/Final/WorkoutHologramPortal.vsh
[12:23:01] Loading Shader WorkoutHologramPortalRing
[12:23:01] ERROR: Missing Vertex Shader asset data/shaders/Final/WorkoutHologramPortalRing.vsh
[12:23:01] Loading Shader FinalCopy
[12:23:01] ERROR: Missing Vertex Shader asset data/shaders/Final/FinalCopy.vsh
[12:23:01] Loading Shader defaultWorld_Terrain
[12:23:01] ERROR: Missing Vertex Shader asset data/shaders/Final/defaultWorld_Terrain.vsh
[12:23:01] Loading Shader defaultWorld_TerrainHeightMap
[12:23:01] ERROR: Missing Vertex Shader asset data/shaders/Final/defaultWorld_TerrainHeightMap.vsh
[12:23:01] Loading Shader shadowmap_TerrainHeightMap
[12:23:01] ERROR: Missing Vertex Shader asset data/shaders/Final/shadowmap_TerrainHeightMap.vsh
[12:23:01] Disabling heightmap shaders
[12:23:01] Loading Shader defaultWorld_instanced
[12:23:01] ERROR: Missing Vertex Shader asset data/shaders/Final/defaultWorld_instanced.vsh
[12:23:01] Loading Shader defaultWorld_notShadowed_instanced
[12:23:01] ERROR: Missing Vertex Shader asset data/shaders/Final/defaultWorld_notShadowed_instanced.vsh
[12:23:01] Loading Shader defaultWorld_instanced_TerrainHeightMap
[12:23:01] ERROR: Missing Vertex Shader asset data/shaders/Final/defaultWorld_instanced_TerrainHeightMap.vsh
[12:23:01] Loading Shader defaultWorld2Layer
[12:23:01] ERROR: Missing Vertex Shader asset data/shaders/Final/defaultWorld2Layer.vsh
[12:23:01] Loading Shader defaultWorld2Layer_instanced
[12:23:01] ERROR: Missing Vertex Shader asset data/shaders/Final/defaultWorld2Layer_instanced.vsh
[12:23:01] Loading Shader accessory_instanced
[12:23:01] ERROR: Missing Vertex Shader asset data/shaders/Final/accessory_instanced.vsh
[12:23:01] Loading Shader defaultWorld_notShadowed
[12:23:01] ERROR: Missing Vertex Shader asset data/shaders/Final/defaultWorld_notShadowed.vsh
[12:23:03] ANT DONGLE NOT CONNECTED
[12:23:03] ANT : Setting network key on network 0...
[12:23:04] ANT : Setting network key on network 1...
[12:23:04] ANT : Setting network key on network 2...
These files do exist. I tried to reinstall Zwift. Same problem.
1 Like
I’m having the same issue…
Zwift worked fine yesterday.
It went to update this evening. Finally updated. then I started to get that pop up
“could not find required data files…”
I’ve uninstalled, and reinstalled… same issue…
1 Like
I think I’ve found the solution! I had to move Zwift to an external drive and than Launch it from there. (I had this issue on a bootcamped Mac)
The steps I followed:
- Open Task Manager and end the process “Zwift Launcher (32 bit)” - mine was usually near the bottom
- Plug in your external drive and move the whole “Zwift” folder from “Program Files (x86)” to your drive
- Delete the files on your computer drive - you won’t need them anymore
- On your external drive navigate to “Zwift” and open “ZwiftLauncher” and it should work now.
- I also created a shortcut to ZwiftLauncher on my desktop but that’s optional.
Hope it helps!
4 Likes
Wow … that worked for me too … I even tried moving it to c:\Zwift and that didn’t work … really did imagine sticking it on an external drive would help at all!?
Come on zwift … what on earth is going on with this?
1 Like
In case any of you do not have access to an external drive or are running into performance issues due to external hard drive bottlenecks, another solution is to create a virtual disk, install Zwift on it and run it from there. I personally implemented it and it has been working flawlessly.
2 Likes
This is the best solution and worked for me.
1 Like
Just wanted to add my own experience with this issue here, I set up a brand new laptop and started encountering the exact same error, “Could not find required data files”. I opened a ticket with Zwift and dozens of emails later, after blaming OneDrive, graphics cards and drivers, hard drives, and everything else under the sun as a reason for the problem, installing Zwift on a virtual disk as Jose recommended solved the issue immediately. Anyone else having this problem, please follow this guidance and avoid the same pain!!
Almost one year later and I have the same problem.
1 Like
Same issues for me. Default installer put zwift in program files (x86) even though zwift itself is 64 bit…??
I tried installing on C:\program files(x86), C:\program files, and C: all with the same issues.
this is the newest 1.21.0 build, with installer 1.1.1, on windows 10. This was the first install of zwift on this particular windows 10 machine. My current pain cave was setup with an older win 7 system which is losing support as of the 1.21.0 build. I really hope there is a solution from the developer, having to use an external drive or a virtual drive is a workaround for a problem that should not exist in the first place.
2 Likes
Zwift program for windows was coded by monkeys. I dare them to prove me wrong.
Disk health is 100% via Crystaldisk.
More than enough disk space
Windows 10 Enterprise N Build 20H2
Having to fix something by dragging it into another folder, something that reminds me of DOS days…
Think ill just uninstall, cancel sub & go with FulGaz
1 Like
it´s 2024 and the virtual hard drive solution still works…
the bad thing is that zwift still hasn´t resolved this issue…
Hi. I’m reporting very old, persisting bug today, again.
Here’re same issues found via quick search here in this forum. THIS IS AT LEAST 5 YEARS OLD ISSUE!!!
For my case, the solution was moving the entire zwift installation to the 512-byte formatted drive. Luckily I have an old SATA SSD formatted 512 bytes native. With all the other newer (not so latest though) NVMe drives with 4K native format, zwift fails to launch. I think this is why they managed to launch the app OK in their external drives or somewhat old ones.
Are you, Zwift devs, investigating this issue? Do you have any plan or solution to resolve this issue?
Added:
Just comfirmed this is a sector size issue. I’ve tested using well-known(??) vhd method with varying logical sector size. Default logical sector size is 512 bytes when creating the virtual hd. With 512 bytes sector drive zwift launches OK, but with 4K bytes sector it fails with same error.
Drives nowadays are moving toward 4K native format fast. Zwift really needs to cope with this trend.
Drive (logical) sector size matters. Funny I’m seeing this kind of compatibility issue today. Check your format settings with admin privilege in cmd:
fsutil fsinfo ntfsinfo c:(drive letter of your zwift installation)
The number displayed in “Bytes Per Sector” row should be 512 to run zwift on that drive. 512 bytes format is quite ancient and modern drives are formatted in 4096 bytes default. Zwift devs really should deal with this compat problem sooner or later.
Hello folks,
I’m sorry to hear this issue has returned (or may still be occurring since 2020). It has been flagged up at HQ for additional investigation. Right now, the best workaround appears to be the community-provided steps marked as a solution on this post.
I’ll share any updates from HQ and provide any additional/easier solution steps that become available.